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

Gradle Community

i kinda doubt you can do that, because the heap space it's talking about, is done at the jvm launch time. that's just the way the jvm works...so the only way to do it that way i guess would be to fork it into another one, similar to what TestKit does

so..i would say: no

why would you want to do it on a per task basis anyways? that seems like premature optimizing for no reason

Some tasks support forking (e.g. `JavaCompile`) and you can then configure JVM arguments for that task (or to be accurate about `JavaCompile`, for a dedicated daemon process that can be reused between tasks and runs)

interesting, didn't know that about javacompile

<https://docs.gradle.org/current/dsl/org.gradle.api.tasks.compile.CompileOptions.html#org.gradle.api.tasks.compile.CompileOptions:fork>