On 1/5/06, Bill Dudney <[EMAIL PROTECTED]> wrote: > Do we really end up with everything from the top level in the lib > dir? What I'm thinking is something like this being in a 'user' project. > > <dependency> > <groupid>org.apache.myfaces</groupId> > <artifactId>tomahawk</artifactId> > </depdency> > > This will cause the transitive dependency thing to pull in everything > that tomahawk depends on but won't touch the top level pom as I > understand it anyway. Am I wrong about this?
I don't know for sure, I'd have to experiment with it. I think that if Tomahawk inherits dependencies, then they "belong" to Tomahawk no matter where they originally came from. If your webapp depends on Tomahawk, you're going to get all of them. > I hate to repeat the info though... Lesser of two evils? :) My first experiences with m2 were fending off unwanted transitive dependencies and submitting patches for poms in the repository so my own webapps would contain the right things. I'd rather do the work up front, and make sure that the users get clean poms that express exactly the right dependencies for each module. And so far the only duplication I'm seeing is from the dependencies that are not transitive (the ones with test or provided scope.) -- Wendy
