Skip to content

Composite build configuration override each other #723

@rlatapy-luna

Description

@rlatapy-luna

🐛 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

  1. 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)
  2. Run MySubProject:refreshVersions alone, ok
image

📱 Tech info

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions