I recommend you build the plugin from source (until a newer version is properly released) and test it. If it does work, than all you need to do is wait for the release (or keep working with the version you built). If it still doesn't work, then that means there really is a bug and you should open a JIRA ticket for it.
To build the plugin from source, you need to: 1. checkout the code from SVN (see http://maven.apache.org/plugins/maven-ejb-plugin/source-repository.html) 2. build the plugin (issue a "mvn clean install" inside its directory) 3. rebuild your project and see if it works Good luck! On Sat, 2006-09-16 at 16:38 +0200, Markus KARG wrote: > Arik, > > I have not customized the version of the plugin in any way, I just > installed Maven 2.0.4 and let it do what it likes to. As I found out, it > is pulling version 2.0 automatically, which seems a bit out of age. > Unfortunately, it seems to be the latest published, while the ejbVersion > feature was introduced in 2.1-SNAPSHOT which is not yet published. > > Is that right? > When will 2.1 be released? > > Markus > > Arik Kfir wrote: > > Hi Markus, > > > > What version of the plugin are you using? Also, a dump of the complete > > error might be useful too. > > > > On Sat, 2006-09-16 at 11:22 +0200, Markus KARG wrote: > > > > > >> Dear Maven Community, > >> > >> Today I have seen on the Maven web site > >> (http://maven.apache.org/plugins/maven-ejb-plugin/ejb-mojo.html) that > >> the ejb plugin is able to package EJB3 compliant JARs. So I wanted to > >> try that out and have set up a sample project. > >> > >> Unfortunately it seems it is not working as expected actually. On the > >> web site it is told that once ejbVersion is set to 3.0 then the > >> ejb-jar.xml would be optional. In fact, when setting the ejbVersion to > >> 3.0, the plugin still complains about the missing ejb-jar.xml and fails > >> to build: > >> > >> Embedded error: > >> /home/markus/.eclipse/sample-ejb/target/classes/META-INF/ejb-jar.xml > >> isn't a file. > >> > >> The pom.xml is attached below, it is written according to the > >> documentation found on the web site. > >> > >> So is this a bug in the plugin or a bug on the web site? > >> > >> Thanks > >> Markus > >> > >> <project xmlns="http://maven.apache.org/POM/4.0.0"; > >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > >> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > >> http://maven.apache.org/maven-v4_0_0.xsd";> > >> <modelVersion>4.0.0</modelVersion> > >> <groupId>local.sample</groupId> > >> <artifactId>sample-ejb</artifactId> > >> <packaging>ejb</packaging> > >> <version>1.0-SNAPSHOT</version> > >> <name>Sample :: EJB</name> > >> <build> > >> <plugins> > >> <plugin> > >> <groupId>org.apache.maven.plugins</groupId> > >> <artifactId>maven-compiler-plugin</artifactId> > >> <configuration> > >> <source>1.5</source> > >> <target>1.5</target> > >> </configuration> > >> </plugin> > >> <plugin> > >> <groupId>org.apache.maven.plugins</groupId> > >> <artifactId>maven-ejb-plugin</artifactId> > >> <configuration> > >> <ejbVersion>3.0</ejbVersion> > >> </configuration> > >> </plugin> > >> </plugins> > >> </build> > >> <dependencies> > >> <dependency> > >> <groupId>javax.javaee</groupId> > >> <artifactId>javaee</artifactId> > >> <version>1.5</version> > >> <scope>provided</scope> > >> </dependency> > >> </dependencies> > >> </project> > >> > > > > >
