Hello, I found this note on the maven wiki: <snip> Attachments and Transitive Resolution We also need a way to distinguish the dependencies that apply when resolved transitively via an attached artifact, rather than the main one. For example, while the server-side component of an EJB may need several dependencies, the ejb-client aspect might only need one or two of those, just enough to fulfill the needs of the EJB interfaces, and give the client the ability to work with the data. However, when a dependency of type ejb-client is declared in a project, the entire dependency set is resolved transitively. </snip>
I totally agree with this. Transitivity is great, but sometime it is just a pain... especially with ejb-clients.. Is there a plan to adress this issue on the futur release of maven ? Like to add a flag to turn on/off transitivity at dependency declaration time: <dependency> <artifactId>..</artifactId> <groupId>..</groupId> <version>1.0</version> <transitivity>false</transitivity> </dependency> This would be so great.... wound't it ? Cheers, -toni -- View this message in context: http://www.nabble.com/Transitivity-on-off-tf4689655s177.html#a13403328 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
