🐛 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 resulting libs.versions.toml files)
- Run
MySubProject:refreshVersions alone, ok
📱 Tech info
🐛 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 inrefreshVersionsblock from main projectsettings.gradle.ktsis overriden by configuration set in included projectsettings.gradle.kts(even if there is no configuration).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
refreshVersionstask (which depends on MySubProject:refreshVersions). Both task run, but both use configuration from MySubProject (check the log and resultinglibs.versions.tomlfiles)MySubProject:refreshVersionsalone, ok📱 Tech info
--scan.