Hi, Oren.
What I did to work around this, is to create the postGoal below in my main maven.xml.
After the ejb is created, this goal uses the was5 plugin to generate an ejb.jar with stubs and replaces the ejb in its original target location. Then this is unjared to the was5 plugin working dir, then jared back into a client jar, with the same exceptions as can be set for the ejb:ejb-client goal. Perhaps a bit messy, but it works well for me!
Harald
<postGoal name="ejb:ejb">
<!--==================================================================-->
<!-- Generate deployment code and stubs in ejb jar -->
<!--==================================================================-->
<attainGoal name="was5:ejbDeploy"/>
<!--==================================================================-->
<!-- Copy jar with deploymentcode back to original -->
<!--==================================================================-->
<ant:copy preservelastmodified="true"
file="${maven.was5.ejbDeploy.file.out}"
tofile="${maven.was5.ejbDeploy.file}"/>
<!--==================================================================-->
<!-- Builds an ejb client jar file -->
<!--==================================================================-->
<ant:unjar
src="${maven.was5.ejbDeploy.file.out}"
dest="${maven.was5.ejbDeploy.workingdir}"
/>
<ant:jar jarfile="${maven.build.dir}/${maven.final.name}-client.jar"
basedir="${maven.was5.ejbDeploy.workingdir}"
excludes="${maven.ejb.client.base.excludes},${maven.ejb.client.excludes}"
index="${maven.ejb.client.index}"
>
</ant:jar>
</postGoal>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
