Mathias, of course, two simple "transitive" flags (one on Configuration and another on Dependency) won't allow you to model all conceivable cases. But that's not the goal. The real question is if they allow you to model the cases that are relevant in practice. Your last example looked very artificial to me. That's why I asked for a use case.
As has been said before, for M2 we will improve transitive dependency management. But please keep in mind that the (re)design of such a feature is influenced by many factors: - What users already know/expect - How the underlying technology works (Ivy in this case) - Needs and limitations of technologies that we integrate with (such as the Groovy compiler) - etc. A general remark: It helps if posts are formulated as clearly and explicitly as possible. For example, your latest post raised the following questions in my head: - Why do you first say that the Jars are included in the War, and then use "providedCompile"? - When you say "It only works if i define it like the following example", which other way of doing it are you (implicitly) referring to? - When you say "Look at the difference between "compile" and "providedCompile", what difference are you referring to? (I still don't have a clue.) - When you say "That was unexpected for me", do you mean it's good? Bad? A bug? Or are you just trying to say that you learned something new? Cheers, Peter -- 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-tp3358303p3361839.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
