From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

I have some plugin code that I need to migrate away from this API due to it now being deprecated.

The code in question gathers information from this callback during the build and generates some reporting t the conclusion of the build (via the also deprecated `buildFinished` hook)

I'm currently digging into task outputs to get report dirs, etc., as part of the data gathering so I actually want the `Task` instance

I suppose I could resolve this by adding task finalizers to all impacted tasks and then feed that info into a build service but am hoping not to do this due to the sheer volume of tasks that would be added to our already insanely large task graph...

(side note: what would be really awesome is to be able to append an Action to a task that runs even on prior action failure)

• create a build service
• make it implement `OperationCompletionListener`
• inject an instance of `BuildEventsListenerRegistry`
• use the latter to register the former for being informed about finish events
• make the build service implement `AutoCloseable` to have a conform replacement for `buildFinished`

That approach doesn't give me access to the `Task` implementations, unfortunately

(well, if it does, I don't see the connection...)

Could be that it doesn't and that this is not supported.
Just some speicific information like outcome, starttime, endtime, ....
If you have a valid use-case you might post a feature request, maybe they can add something.

Roger that.  I haven't seen an appropriate API but was fishing here to see if I missed anything.

I imagine they don't want to expose `Task` since it is mutable and _could_ be used to change something that would impact configuration-time.

yeah `Task` is a mutable object that comes with a lot of baggage. the whole point is to not expose `Task` and friends

still waiting on an alternative for  `beforeTask` myself