The following comment has been added to this issue:
Author: Felipe Leme
Created: Tue, 31 Aug 2004 3:29 PM
Body:
BTW, currently, the existing properties don't carry the version:
maven.war.final.name = ${pom.artifactId}.war
maven.ejb.final.name = ${maven.final.name}.jar
Wouldn't it be better to add the version, as above?
maven.war.final.name = ${pom.artifactId}-${pom.currentVersion}.war
maven.ejb.final.name = ${maven.final.name}-${pom.currentVersion}.jar
The only drawback I can see of adding the version is the name of the application when
it's deployed. For instance, if I deploy a project-x.y.z.war on JBoss or Tomcat, it
would be accessed as /project-x.y.z, instead of /project. But the version number is
added anyway on installs and deploys, so I think we should add it to the property (so
it's included in the war/ejb-jar generated at target).
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPJAVA-8?page=comments#action_23633
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPJAVA-8
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPJAVA-8
Summary: Consistent properties for jar, war, ejb and ear
Type: Improvement
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-java-plugin
Assignee:
Reporter: Aslak Hellesoy
Created: Tue, 25 Mar 2003 5:11 AM
Updated: Tue, 31 Aug 2004 3:29 PM
Description:
The current naming conventions for properties defining the names of jar, ejb, war and
ear are somewhat inconsistent.
This patch introduces 4 new properties:
# defined in the java plugin's plugin.properties
maven.jar.final.name = ${maven.final.name}.jar
# defined in the war plugin's plugin.properties
maven.war.final.name = ${maven.final.name}.war
# defined in the ejb plugin's plugin.properties
maven.ejb.final.name = ${maven.final.name}.jar
# defined in the ear plugin's plugin.properties
maven.ear.final.name = ${maven.final.name}.ear
This patch solves the following problems:
1) It removes the risk of name clashes for projects that produce both plain
jar files and ejb jar files, since the maven.ejb.final.name property can be overridden.
2) When packaging wars and ejbs inside ears, it is sometimes desirable to have
different names for ejbs and wars, like foo-ejb-1.0.jar and foo-war-1.0.war. This is
necessary when the contents of an ear file is to be deployed on different weblogic
servers with weblogic.deploy. This can now be achieved by overriding
maven.ejb.final.name and/or maven.war.final.name.
This patch should not change any of the current functionality, and the documentation
has been updated too.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
