artifact:install and custom jars/EAR tag

[Darren Hartford <dh...@ghsinc.com>]

Hey all,
I'm trying to setup WSR's as part of my process, and in trying to remain true to maven NOT use the ant-copy task.  So, I have this:

<postGoal name="ejb:install">
<artifact:install
artifact="${basedir}/target/${pom.artifactId}-WSR-${pom.currentVersion}.wsr"
type="wsr"
project="${pom}"/> 
</postGoal>

The .wsr is a JAR file with a different extension.  As found when using the EAR task, I can not have an EJB/JAR/WSR with the same artifactId even if they have different extensions, so I thought I could simply change the artifact filepath that it should copy...but it didn't work. 

The file called MYSESSION-WSR-1.0.wsr created (and verified) in the /target directory is instead changed back to MYSESSION-1.0.wsr when installed into the Repository.  Since the task that creates the EJB and the WSR are the same sub-project (and in fact the same Maven task), can not (should not?) change the artifactId itself.

In keeping true to maven (i.e. not working around with an ant-copy task), please advise how to handle this little dilema. 

-D

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org