Expected and Results
nmcp throws an error if projects have the same name, for example if the root project is called :foo and there's a subproject :bar:foo.
A problem occurred configuring root project 'foo'.
> Nmcp: some projects have the same name: '${it.name}'. This creates issues when resolving the aggregation.
You can usually resolve this error by renaming your projects (including possibly your root project).
Or you can disable this check by calling `allowDuplicateProjectNames.set(true)`.
See https://github.com/gradle/gradle/issues/36167 for more details.
However, in my case the error is not valid. The two subprojects have distinct project.group values. A distinct group allows Gradle to differentiate the projects correctly.
// build.gradle.kts
group = "root"
// foo/build.gradle.kts
group = "foo"
Can the warning be updated to check if the name and group of projects clash?
Related environment and versions
No response
Reproduction steps
No response
Anything else?
'${'$'}{it.name}' -- oops!
|
Nmcp: some projects have the same name: '${'$'}{it.name}'. This creates issues when resolving the aggregation. |
Expected and Results
nmcp throws an error if projects have the same name, for example if the root project is called
:fooand there's a subproject:bar:foo.However, in my case the error is not valid. The two subprojects have distinct
project.groupvalues. A distinct group allows Gradle to differentiate the projects correctly.Can the warning be updated to check if the name and group of projects clash?
Related environment and versions
No response
Reproduction steps
No response
Anything else?
'${'$'}{it.name}'-- oops!nmcp/nmcp/src/main/kotlin/nmcp/internal/DefaultNmcpAggregationExtension.kt
Line 70 in 68fbd33