Actually I didn't want to have a ejb-jar.xml any longer with EJB3. What about the status of that ejb3 plugin: When will it be finished? I mean, this is a thing I expect Maven to do for me.
Takashi Nishigaya wrote: > The maven-ear-plugin does not recognized the jar project as ejb3 module. > If you plan to create ear application with ejb3 modules, the ejb3 > project should declare <packaging>ejb</packaging> in the pom.xml, and > prepare the empty ejb-jar.xml declaring ejb3 schema namespace. > > src/main/resources/META-INF/ejb-jar.xml: > > <?xml version="1.0" encoding="UTF-8"?> > <ejb-jar > xmlns = "http://java.sun.com/xml/ns/javaee"; > xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation = "http://java.sun.com/xml/ns/javaee > http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"; > version = "3.0"> > </ejb-jar> > > This will work well with glassfish. > > Thanks, > Takashi Nishigaya > > Alexander Sack wrote: >> I use packaging type "JAR" for all EJB3 builds as its just easier then >> trying to retrofit the current ejb plugin. >> >> -aps >> >> On 9/6/06, Alexandre Russel <[EMAIL PROTECTED]> wrote: >> >>> >>> >>> > According to "BetterBuildsWithMaven.pdf" I switched from >>> > <packaging>ejb</packaging> to <packaging>ejb3</packaging>. >>> Unfortunately >>> change it to jar. >>> Alex >>> >>> >>> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
smime.p7s
Description: S/MIME Cryptographic Signature
