Closed bartekpacia closed 1 year ago
hi, thank you for report. just for clarification -- are we talking about optimising 0.116s here ?
Yes, but this is on my M1 MacBook – I'm sure there are many people on slower machines where this 0.116s could become e.g 0.5s.
Also, this change usually isn't hard - Gradle docs explain it very clear.
I can make a PR when I find some time :)
thx, will wrap into project.getTasks().register
during pending plugin maintenance
Issue details
robovm-gradle-plugin
creates all its Gradle tasks eagerly, which is bad for build performance.See also:
Reproduction steps/code
Follow steps described in Gradle guide – Avoiding unnecessary task configuration.
I run
./gradlew :help --scan
and it was easy to see that this plugin registers its task eagerly:Configuration
RoboVM Gradle plugin 2.3.18