Add first-class support for included/composite builds
See original GitHub issueRight now, included builds are treated like regular projects, which means their versions are separate from the the project that includes them.
While this is great when you want to keep the projects decoupled, it’d be great to also have the option to share the setup, the versions.properties
file, and have runs of the refreshVersion
task also refresh the versions from all included builds that opt-in to this behavior.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:49
- Comments:9
Top Results From Across the Web
Composing builds - Gradle User Manual
A build that is included in a composite build is referred to, naturally enough, as an "included build". Included builds do not share...
Read more >How to use Composite builds as a replacement of buildSrc in ...
To inform Gradle of the new module that is included, we add the following into settings.gradle : The first line is added for...
Read more >Webinar: Composite Builds with Gradle and IntelliJ IDEA
Composite Builds is a feature introduced in Gradle 3.1 to provide a way to decompose large multi-project builds into smaller, more isolated ...
Read more >Webinar Recording: Composite Builds with Gradle and IntelliJ ...
Support for composite builds was first introduced in IntelliJ IDEA 2016.3, with this you had the ability to add additional Gradle builds to ......
Read more >Composite, included build, dependency substitution to project ...
Included builds are for substituting binary dependencies. Something that you could also publish to a repository and use from there instead. So ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
dirty experiment to see if refreshVersions can automatically set up task dependencies on refreshVersions in included builds
I don’t see how the version entry usage comments would be removed.