On Thu, October 25, 2007 11:50 am, Antonio Parolini wrote: > 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 ?
Unfortunately not - with transitivity turned off, you now move from an EJB client will too many dependencies to an EJB implementation with too few dependencies, and code that doesn't build. :( Using EJB3, we have approached this by declaring the EJB client interface in its own project, and the EJB implementation in a second project. Being different projects, they can export different sets of dependencies. (It also solves the problem of people arbitrarily changing the interface) To get this to work in JBoss, we needed to make sure that the EJB client interface was also declared as an EJB in itself. The two EJBs (EJB-client and EJB) where then deployed into the ear file, and it works great. Regards, Graham -- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
