Open iamdanfox opened 5 years ago
It looks like dependencySubstitution
takes an Action<DependencySubstitutions>
, not a Closure, and module
is a method on that DependencySubstitutions
.
Not sure how or when groovy decides to implicitly look up things in the only argument of a functional interface.
The error messages seem to suggest that the innermost closure isn't looking at that method's parameter (the DependencySubstitutions
) when trying to decide where module(String)
comes from...
What happened?
In a repo using nebula dependency recommender, we used the following snippet to make
com.palantir.baseline-class-uniqueness
pass:After switching to gradle-consistent-versions, I hit this:
Then fiddling with closures:
What did you want to happen?
Either this syntax should be magically work fine (and not barf on the
subprojectUnifiedClasspathCopy
), or we should provide a clear recommendation for how to achieve these workflows.