I was hoping I could handle it transparently, but it looks like this hasn't been fully implemented in the ejb plugin yet.
What I'd really like is to set a property in a project, and the ejb:ejb, ejb:install, etc. goals then all include additional steps for the ejb-client jar. Does this sound reasonable?
Before I go and patch the plugin, does anyone have recommendations, existing workarounds, or their own requirements to add? Are there any other plugins that currently produce (and install/deploy) multiple artifacts?
Matt
James CE Johnson wrote:
Thoughts on creating the client JAR for an EJB?
? Separate projects with individual artifacts?
? Single project with two artifacts?
We tend to take the second approach since they share some code (DAOs and such). We also make heavy use of xdoclet and we wouldn't want to do that twice.
<goal name="ejb:client-jar" prereqs="test:compile, ejb:jar"> <mkdir dir="${maven.build.dir}/test-classes" /> <jar jarfile="${maven.build.dir}/${maven.final.name}-client.jar" basedir="${maven.build.dest}" excludes="**/*Bean.class,**/*CMP.class,${maven.jar.excludes}" manifest="${maven.build.dir}/ejb-manifest" > <fileset dir="${maven.build.dir}/xdoclet/ejb" includes="META-INF/**"/> <echo>We should probably change this.</echo> <fileset dir="${maven.build.dir}/test-classes" includes="**/*.class **/*.xml" /> </jar> </goal>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
