You need to provide good metadata for your projects. Maven defaulting principles work quite fine if you respect that.
If you project builds an ejb, the packaging type must be ejb. If you don't, Maven can't understand in other modules (that depend on it) what to do with the dependency. Typically, the ear plugin takes care of ejbs and will generate the deployment descriptor automatically if you need one. 2 is the solution and 1 seems more like a hack to me. HTH, S. On Fri, Apr 3, 2009 at 5:49 PM, Jean-Claude <[email protected]>wrote: > > Hi, > > I want to build an EAR file with modules. All EJB modules have been defined > as jar (<packaging>jar</packaging). > What is the best way: > > 1). > Include those EJB modules in the EAR file using <jarModule> > > or > > 2). > Change the packaging of all EJB modules to ejb (<packaging>ejb</packaging>) > and then include those EJB modules in the EAR file using <ejbModule> > > What are the advantages or disadvantages of each solution? > > Thank you for your Help! > -- > View this message in context: > http://www.nabble.com/maven-ear-plugin%3A-jarModule-or-ejbModule-tp22871170p22871170.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck" -- S.Yegge
