Let's say that I have a dependency on project A and project B, and that
both have a dependency on project LOG.
So I declare a dependency on those in my POM, and the transitive
dependency mechanism will get me also LOG... but which version?
If I want to specify the version I want, I can add LOG as a /direct/
dependency.
Then some time passes, and A and B loose the dependency on LOG. I still
have it in my direct dependencies, and I will still be downloading it
and adding it to the classpath, even if it is not needed. Imagine this
for a tree of transitive dependencies...
IMHO there should be a distinction between direct and transitive
dependencies in the POM. I should be able to *suggest* the version of
the transitive dependencies to use, but not have it included in the
cleaapath if no direct dependency references it.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
