Thank you for your quick answers, Use the dependencyManagement section seems a little bit cumbersome to implement, because it implies to define a parent POM for all libraries to which I would apply this "retention classes" mechanism.
It's somewhat speculative on my part, but It could be very convenient to provide a new scope (or an option like "optional") that allows Maven to change the scope of "z" dependency to "runtime" when the artifact "A" is included as dependency of project "B". I think it would be an interesting feature. What do you think about this idea ? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
