You can use the dependency:tree (from the latest snapshot version). You can detect some of these errors using dependency:analyze-dep-mgt (if it finds a dependency that was excluded anywhere, it will warn you) and you can enforce it in the build using the enforcer noBannedDependencies rule.
________________________________ From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Tue 7/24/2007 3:25 PM To: Maven Users List Subject: Re: Exclude a dependency without knowing where it's from Not that I'm aware of. Try "mvn -X ..." then search the output to see which dependency(-ies) are bringing in the dep. Then add the exclusion to those deps directly. Wayne On 7/24/07, lightbulb432 <[EMAIL PROTECTED]> wrote: > > How do you exclude a JAR file "A" when you don't know what dependency B > transitively includes A as a dependency? I have a lot of dependencies that > Maven gets from the public and internal repositories - naturally, Maven > retrieves its dependencies too. > > Rather than looking through 75 POM files to figure out which includes "A", > is there a way to say in my POM to never include "A" regardless of who > declares it as a transitive dependency? > > Thanks. > -- > View this message in context: > http://www.nabble.com/Exclude-a-dependency-without-knowing-where-it%27s-from-tf4137998s177.html#a11769693 > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
