Closed lptr closed 10 years ago
A solution could be to create a proper project configuration instead of a detached one, maybe suffixing the name of the target configuration with _pride
.
A disadvantage of this solution is that there could be unintended consequences of build authors not expecting Pride to create its own configurations. An advantage is that this way the user can get some feedback about which dynamic configurations Pride is currently trying to resolve.
Or we could use Configuration.copy()
.
Configuration.copy()
is great, because that way we get all the benefits:
ResolutionStrategy
(among other things)Copy
suffix, but that's still better than detachedConfiguration2
)
The Gradle manual recommends changing dependency caching like this:
However, this doesn't apply to the detached configurations Pride creates when resolving transitive dependencies, and this can mess with the whole resolution logic.