our maven.xml looks like this
<project xmlns:deploy="deploy" xmlns:j="jelly:core">
<goal name="lib">
<deploy:copy-deps todir="lib"/>
</goal>
<goal name="copy.dep" description="copy dependencies">
<j:forEach var="dep" items="${pom.dependencies}">
<echo>${dep.getArtifactId()}.${dep.getExtension()}</echo>
<copy file="${pom.getDependencyPath(dep.getId())}" tofile="lib/${dep.getArtifactId()}.${dep.getExtension()}"/>
</j:forEach>
</goal>
</project>
On Oct 19, 2004, at 11:15 AM, STRAYER, JON (SBCSI) wrote:
Hi,
Maven creates jar, but with name "PROJECT-version.jar" eg:- PROJECT-12.0.0.jar, is there anyway i can override this to create "project.jar"
This is not something which you would normally want to do with maven. Jars and other artifacts are versioned for numerous good reasons.
How many people here are running their applications outside of a container?
How do you handle setting the class path (when it changes with each release)?
I ended up taking some code from the maven deploy plugin and modifying it to generate a class path from the pom.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--ming
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
