On 8/8/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
Why should I have to declare it in the app, when I've declared it at the parent level? What's the point of transitive dependencies if they do not work the way you want, and there's no way to force them to do so?
I should have been more clear. It is not that transitive dependencies are bad ... it's that I believe inherited dependencies (including version dependencies described by <dependencyManagement> sections should *always* override transitive dependencies on the same artifact. Alternatively, it would be reasonable to allow an override of whatever the default behavior is for advanced cases ... but requiring me to define version overrides in leaf nodes, simply because my inheritance hierarchy is deeper than my dependence hierarchy, encourages bad build architecture design behavior -- and isn't part of the point of Maven to eliminate that kind of idiocy? :-) Craig
