Then to install the deployed jar, replacing the normal target jar, use
something like this..
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-install-plugin</artifactId>
<version>2.3</version>
<executions>
<execution>
<id>install-library</id>
<phase>install</phase>
<goals>
<goal>install-file</goal>
</goals>
<configuration>
<groupId>${project.groupId}</groupId>
<artifactId>${project.artifactId}</artifactId>
<version>${project.version}</version>
<packaging>jar</packaging>
<file>${basedir}/working/FileNameEJB-deployed.jar</file>
</configuration>
</execution>
</executions>
</plugin>
Hi Ken,
I came across this error, I got around it by downloading the plugin sources
and changing the EjbDeployMojo.java to log warnings instead of throwing an
exception.
Like you say the deployed jar has the generated code in anyway so I am
unsure of the need to copy the sources, and why a failure to do so should be
terminal. Maybe a plugin developer could shed some light on this?
--
View this message in context:
http://n2.nabble.com/maven-ejb-plugin---was6-maven-plugin-generated-jar-files-tp2639579p3093071.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]
