build-tool-roadmap
build-tool-roadmap copied to clipboard
gradle
Gradle Build Tool roadmap
Complete overhaul and re-write of https://docs.gradle.org/ with personas and user levels in mind: 1. Software Developer - Level 1 2. Build Engineer - Level 2 3. Plugin Develop - Level...
The EAP should have * A vanilla AGP build working end to end in Studio * Using the AGP model, no prototype plugins * May require special nightly of AGP...
* Create a report from the problems collected during the build * Enable this report by default
### Summary / Manifesto The Gradle daemon will now require Java 17 to run. Previously, Java 8 was required. This will result in Gradle refusing to start a build if...
### Summary / Manifesto Gradle will enable users to request that the selected toolchain can provide the native image capability. ### References In Gradle: * gradle/gradle#32613 In the Foojay provisioning...
The Problems API should allow clients to report deprecations. Specification: https://docs.google.com/document/d/19NiSuFJIWrVQJUYvuoY4ePM79IUuIow31R3k1Z1zBSU/edit?tab=t.0#heading=h.wbxzemi759rh
### Summary / Manifesto In order to enable plugin authors to build plugins for different Gradle versions, Gradle will publish its API so it can be used as a dependency....
### Summary / Manifesto Enable Java 24 support in Gradle, both through toolchains and by running Gradle itself on Java 24. ### References _No response_ ### Discussion Channels _No response_
After implementing the remaining missing feature (see the other items on the board), the Problems API should be reviewed and marked as stable.
Following the [second EAP](https://github.com/gradle/build-tool-roadmap/issues/90). * Demonstrate composability/extensibility with Software Types. * Support additional features in DCL syntax (collections, files, container defaults ) The target date is February 2025.
