New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃悩 Declarative Gradle #28337
Labels
Comments
oleg-nenashev
added
a:feature
A new functionality
a:epic
roadmap
Initiative on the public Gradle roadmap
and removed
to-triage
labels
Mar 4, 2024
ov7a
added
in:declarative-dsl
and removed
a:feature
A new functionality
to-triage
labels
Mar 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At Gradle, part of our vision is to provide an elegant and extensible declarative build language that enables expressing any build clearly and understandably. We are working on Declarative Gradle to realize that part of the vision.
Our key principles are:
Software developers should be able to define any software in a clear and understandable way so that they can build their software without the need to understand the details of how the build system works.
Build engineers should maintain the current level of flexibility and be able to automate a wide range of software build automation scenarios with custom build logic.
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 software definition automatically or through UI reliably.
Concept
This is how Declarative Gradle could look like:
Expand code
References
Discuss
#declarative-gradle
on the Community SlackStatus
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!
Key milestones
The text was updated successfully, but these errors were encountered: