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. -- Peter Niederwieser Developer, Gradle http://www.gradle.org Trainer & Consultant, Gradle Inc. http://www.gradle.biz Founder, Spock Framework http://spockframework.org -- View this message in context: http://gradle.1045684.n5.nabble.com/Define-transitive-dependencies-for-subprojects-tp3358303p3359871.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
