Hi Peter,
thank you for your explanation. I expected the behavior of the second
case also for the first case.
But now I have a question.
If I have two compile project dependencies, how can I define the
behavior of the second case?
dependencies {
compile (project(':J1')) {
transitive = false
}
compile (project(':J2')) {
transitive = true
}
}
compile: J1, J2, dependencies of J2
runtime, testRuntime, ...: J1, dependencies of J1, J2, dependencies of J2
regards,
Mathias Kalb
Am 27.01.2011 16:15, schrieb Peter Niederwieser:
The first case is clear. The project dependency added to the compile
configuration has transitive resolution disabled. This also affects
configurations extending from compile, because they see the very same
dependency (aliasing effect).
In the second case, the question is what "compile.transitive = false" should
mean to configurations extending from compile. The current behavior makes
sense to me. For example, if you want to be strict about compilation and
only put explicitly listed dependencies on the compile class path, you might
nevertheless want transitive dependency resolution for the runtime class
path.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
