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

Gradle Community

You could consider doing the ramp up not in the constructor, but in a method you call from first, so that if the service is created earlier you do not do the ramp up too early. (Don't forget a check to not do it multiple times then)

And if you need a tear down, you would do it in close of AutoCloseable

The concurrent usage of the service is simply prevented by not executing the tasks in parallel, which is why you can use a service for this serial-making.

But the actual use has to be an actual use

A task could have some condition whether it needs the service or the task could be skipped and then initializing the service would be wasted cycles and Gradle does not want to waste cycles. :-)

yeah that makes sense :slightly_smiling_face:
&gt; You could consider doing the ramp up not in the constructor, but in a method you call from first, so that if the service is created earlier you do not do the ramp up too early.
In my scenario both are equivalent, but I see how for a complex service it's good to keep it in mind :+1: thanks!

&gt; The concurrent usage of the service is simply prevented by not executing the tasks in parallel, which is why you can use a service for this serial-making.
sure, although one could argue that a task is not using a service if it's not _using_ it :wink: I do like the functionality, just noting inconsistency. You can argue both ways that a service is used if it's declared as such _or_ when it's actually used and both make sense. I guess concurrency feature is common enough to warrant easier setup

&gt; In my scenario both are equivalent, but I see how for a complex service it's good to keep it in mind :+1: thanks!
Well, not you control when the service is instantiated, Gradle does.
But you control when you would call the ramp up method. :slightly_smiling_face:
:man-shrugging:

&gt; sure, although one could argue that a task is not using a service if it's not _using_ it
While we are at splitting hairs, it was not written that as soon as the task uses the service other tasks cannot use it at the same time.
It was just said that Gradle does not allow more than the given amount to use it at the same time.
And Gradle does this by not starting the task at all.
So no inconsistency if you read it the right way. :slightly_smiling_face: