Composite build configuration override each other
rlatapy-luna opened this issue ยท 1 comments
- I have read the guidelines for submitting issues
๐ Describe the bug
I know composite build is not officially supported, but:
When including a project in another one by using a Gradle composite build (includeBuild
), configuration set in refreshVersions
block from main project settings.gradle.kts
is overriden by configuration set in included project settings.gradle.kts
(even if there is no configuration).
โ ๏ธ Current behavior
When running refreshVersions task, the configuration set in settings.gradle.kts is not applied
โ Expected behavior
Each projects/included projects use its own configuration without overlapping each other
๐ฃ Steps to reproduce
Here is repro project https://github.com/rlatapy-luna/CompositeRefreshVersions
- Run
refreshVersions
task (which depends on MySubProject:refreshVersions). Both task run, but both use configuration from MySubProject (check the log and resultinglibs.versions.toml
files) - Run
MySubProject:refreshVersions
alone, ok
๐ฑ Tech info
- Build Scan URL
โ ๏ธ It works as expected when using build--scan
.
Hello/Bonjour !
I have a plan to resolve this, but it's quite an undertaking, and since I'm the only "active" maintainer at the moment, don't expect it this year.
However, if you want to contribute it in a way that I'd accept merging, I can give time to help on that so you know how to do it, where to plug things, and avoid Gradle tough tricks.