At Gradle, part of our vision is to provide an elegant and extensible declarative build language that enables expressing any build in a clear and understandable way. We are working on Declarative Gradle to realize that part of the vision. This is an experimental project, stay tuned for updates!
Learn more in the Declarative Gradle Announcement blog post.
- Ease of use for regular software developers. Software developers should be able to define any software and build their projects without the need to understand the details of how the build system works.
- Complete flexibility for build engineers and advanced users. Experienced Gradle users should maintain the current level of flexibility and be able to automate a wide range of software build automation scenarios with custom build logic.
- Excellent IDE integration. Importing the software project to the IDE and interacting with it should be fast and fully reliable. IDEs and other tools should be able to change the definition automatically or through UI reliably.
We implement those principles through a declarative DSL which is, at the moment, based on Kotlin. The Declarative Gradle Announcement outlines more details about the project and the new Declarative DSL we are building.
Declarative Gradle is an experimental project. Currently, no compatibility is guaranteed, and there is no commitment to the DSL syntax and available features. More information will be released soon. Any feedback is welcome! See more on the Contributor Guide.
Here are a few very brief examples of what the Declarative Gradle syntax may look like. As noted above, this syntax is experimental and might change during the experiment.
A typical Java library, which targets a single version of Java, might look like this:
javaLibrary {
publishedAs("my-group:my-lib:2.0")
dependencies {
api("some:lib:1.2")
implementation(projects.someLib)
}
// This library targets Java 21 only
java(21)
tests {
unit {
dependencies {
implementation("some:other-lib:1.4")
}
}
}
}This example shows the definition of a Java library that targets both Java 11 and 21:
Show Code
// Declare the type of software that the project produces
// There is no plugin application, as Gradle infers this from the "javaLibrary" type definition
javaLibrary {
// All information about the library is grouped here
// GroupID/ArtifactID/Version for publishing
publishedAs("my-group:my-lib:2.0")
// Common dependencies for all targets
dependencies {
api("some:lib:1.2")
implementation(projects.someLib)
}
// A library might have more than one target
targets {
// All information about specific targets is grouped here
// Declare Java 11 as a target
java(11) {
// Specific information about Java 11 target
// An additional dependency that is used only for Java 11
dependencies {
implementation("some:back-port-lib:1.5")
}
}
// Declare Java 21 as a target, with no additional information
java(21)
}
tests {
// All information about the tests is grouped here
unit {
// Dependencies for the unit tests
dependencies {
implementation("some:other-lib:1.4")
}
}
}
}See the Getting Started Guides.
Here are the experimental prototypes currently available for initial review and evaluation:
- Declarative Gradle Prototype - prototypes of plugins for JVM, Android, Kotlin and KMP projects built using "unified" plugins that all utilize a similar model and implemented using the Declarative DSL
- Now In Android - a port of a popular Android demo app that showcases the Support for Android in Declarative Gradle.
- Other Early prototypes - Initial prototypes were created for feedback and discussion purposes.
All text/documentation content is open source and licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 License. Some code samples may be licensed under the Apache License v2.0 or other permissive OSI-compliant licenses.
#declarative-gradlechannel on the Gradle Community Slack- Dedicated category Gradle Forums
See Gradle Community Resources for the links to the channels.