The following comment has been added to this issue: Author: dion gillard Created: Sun, 3 Aug 2003 9:42 PM Body: Is this still an issue? --------------------------------------------------------------------- View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-349 Here is an overview of the issue: --------------------------------------------------------------------- Key: MAVEN-349 Summary: Consistent properties for jar, war, ejb and ear Type: Improvement Status: Unassigned Priority: Major Time Spent: Unknown Remaining: 0 minutes Project: maven Components: plugin-java plugin-war Versions: 1.0-beta-9 Assignee: Reporter: Aslak Hellesoy Created: Tue, 25 Mar 2003 5:11 AM Updated: Tue, 25 Mar 2003 5:11 AM 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]