I’m finding it incredibly difficult to keep binary dependencies out of a multi-project build, where a dependency is both a project dependency, and declared as a dependency for a published artifact. It causes jars to be included in the configuration and failures like these:
- IDEA plugin failures - http://issues.gradle.org/browse/GRADLE-2713 * Problems resolving project configuration against a binary dependency - http://issues.gradle.org/browse/GRADLE-2713
Why don’t the project dependencies replace the binary dependencies? These are technically conflicts and I’d expect the project dependency to always win. Is there any way to replace these binary dependencies w/ project dependencies manually (I looked at ResolutionStrategy, but it only takes a notation as a replacement it seems).
This functionality would also allow builds that automatically replace artifact w/ project dependendencies, avoiding the workarounds like this. Is there an improvement ticket for this specifically - it’s really critical for multi-project builds, given how much breakage this can cause.