Daniel Lacasse
Daniel Lacasse
An experimentation of this work is under Nokee, there are still quite a bit of open questions so we will unscheduled it for now.
Starting with Gradle 7.0, a new service was introduced `DependenciesAccessors`. This service is queried (created) in the `beforeEvaluated` project hook. Gradle seems to be dynamically loading APIs (such as JARs)...
We may be forced to rerelease the Gradle APIs for version 7.+ with a patch to the API. I don't want to start patching the API, but if it's the...
Instead of fixing internal APIs, we could allow some way to mock `Project`, `Settings` and `Gradle`. Assuming we split unit, integration and functional testing across the following boundaries: - Unit...
We should investigate if we can position the generated JARs (copy) to the correct place (without colliding with actual Gradle JARs) so the assumption baked into Gradle can still work.
The low ceremony plugin development would allow the normal `dev.gradleplugins.java-gradle-plugin` and `dev.gradleplugins.groovy-gradle-plugin` to be applied in the `settings.gradle[.kts]` as settings plugins. It would configure the root project and disallow any...
Before we can make this useful, we will need a model for build script which we can pass to the methods such as `usingBuildScript`/`usingSettingsFile`/`usingInitScript`. With that, we could run Gradle...
An experimentation of this work is under Nokee, but there are still quite a bit of open questions.
That's a good point. I'm a bit uneasy with how the parameters are configured, but I agree we should be able to specify custom JVM arguments up to a point....
Solving this issue will allow us to stop maintaining the Gradle API redistribution in favour of generating the JARs on the fly. We may still want to release the API...