Yes, I agree with that... and that's a good reason for using
<excludes>. But you don't really disable transitivity completely with
it. You just select from the list of dependencies to not use, in your
example, library B.
Sebastien Brunot wrote:
Even if the POM are correct, transitivity can copy much more classes
than really needed : you're using library A, which a subset of class
uses library B. If you don't use this particular subset of classes in
library A, you don't need the dependency on library B (I hope it's
clear).
Sebastien
-----Original Message-----
From: Edwin Punzalan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 07, 2006 5:53 PM
To: Maven Users List
Subject: Re: Transitive dependecies
Dependencies should be marked as optional if it is not required.
There's nothing bad with transitivity if the poms are correct... it
actually makes dependency management easier.
Broken poms make transitivity look bad.
Wendy Smoak wrote:
On 11/7/06, Sebastien Brunot <[EMAIL PROTECTED]> wrote:
transitive dependencies can be a real pain when you have a lot of
external dependencies in your project. Using <exclusions> tags is a
tedious operation in this case, so I was wondering if a quicker way
exists...
Having to use a lot of exclusions generally means that the poms are
broken. (For example, things that should be marked optional, aren't.)
What dependencies are causing problems?
---------------------------------------------------------------------
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]
