Hi Todd, we use a common parent pom where we define both artifacts in a dependencySection. For the ejb-client we use additional excludes to drop all the unwanted dependencies. Looks good in first place, but triggers another bug: http://jira.codehaus.org/browse/MNG-1797
- Jörg Todd Nine wrote on Wednesday, June 07, 2006 6:49 PM: > Hi all, > I'm declaring an EJB client with the following decencies in > a webapp, and > the common interfaces and beans for parameters and return values > > > <dependency> > <groupId>ata.partnership</groupId> > <artifactId>partnershipCommon</artifactId> > <version>1.0.0-SNAPSHOT</version> > </dependency> > <dependency> > <groupId>ata.partnership</groupId> > <artifactId>partnershipEJB</artifactId> > <version>1.0.0-SNAPSHOT</version> > <type>ejb-client</type> > </dependency> > > This works for requiring the EJB client, however, I'm also receiving > partnershipBusiness, partnershipDataAccess, etc etc. These > are all required > in my EJB, but I don't want these transitive dependencies to > be deployed on > the remote client (The webapp). Short of an excludes directive in the > webapp when I declare the ejb client dependency, is there any > parameter I can use in the EJB plugin to exclude all decencies of the > EJB > on the client > side when I build the ejb client? > > Thanks, > Todd --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
