[GRADLE-1898] Runtime dependency ignored when another dependency already depends on a different configuration of the same dependency which is processed first Created: 07/Nov/11 Updated: 04/Jan/13 Resolved: 09/Nov/11
Consider the attached multiproject.
On the other hand, A has a compile dependency on the custom configuration of B.
However, since the root project explicitely depends on project B (default configuration!), I would expect to find B.jar in the root project war too!
In real-world cases, if B-custom.jar is a stripped-down version of B.jar, the resulting war has an incomplete classpath.
|Comment by Davide Cavestro [ 07/Nov/11 ]|
This seems an annoying regression cause both milestone-3 and milestone-4 produce a WAR with the following contents