Sterling Greene
Sterling Greene
@bot-gradle merge
We will revisit this after 9.0
We don't want to add more special case status handling. It may be possible to mimic this behavior with a ComponentSelection rule that looks at this attribute.
Like Louis said, the force behavior no longer exists and rich versions are preferred. We'll try to document/call this out with an appropriate solution in our docs.
What's the size of `allDependencyConstraints` here? ``` def allDependencyConstraints = project(":platform").configurations.api.allDependencyConstraints.toList() configurations.getByName("earlib").dependencyConstraints.addAll(allDependencyConstraints) ``` In this case, is `:platform` a Gradle platform project that defines constraints? IIUC, you're trying to enforce...
@patrickneulichedldmde would it be possible for you to slim this down into a reproducer or set a breakpoint in https://github.com/gradle/gradle/blob/da8bb2c4e8e73fdfa02cbf485ce1c1e5d52bc781/platforms/software/dependency-management/src/main/java/org/gradle/api/internal/artifacts/dependencies/AbstractDependencyConstraint.java#L27 and tell us how large the onMutate set gets in...
There are a couple of things going on here: - Sharing Dependency/DependencyConstraint instances across multiple configurations and projects - Disabling transitive on a configuration makes platforms kind of useless (because...
We're not advertising this in the release notes.
We'll take a look at this closer. We want to update to v2. It'll take us a bit to get to this.
@jvandort can you see if this has any breaking changes that would require it to be in 9.0?