Message: A new issue has been created in JIRA.
--------------------------------------------------------------------- View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPWAR-21 Here is an overview of the issue: --------------------------------------------------------------------- Key: MPWAR-21 Summary: war-plugin should be able to add manifest Class-Path Entry for dependencies Type: Improvement Status: Open Priority: Trivial Original Estimate: 1 hour Time Spent: Unknown Remaining: 1 hour Project: maven-war-plugin Assignee: Jason van Zyl Reporter: Augustinus Deimel Created: Wed, 24 Mar 2004 4:43 AM Updated: Wed, 24 Mar 2004 4:43 AM Description: In the ejb-plugin we have the possibility to set the manifest Class-Path - Entry. The war-plugin should be able to do this accordingly. It should be possible to set the Class-Path-Entry WITHOUT bundling the dependencies. Generally it would be a good idea to centralize the manifest-Building somehow; currently manifest-buildung is done in different ways in jar, war, ear - plugins My simplified change of war:war is " <j:forEach var="dep" items="${pom.dependencies}"> <j:if test="${dep.getProperty('tmobile.war.manifest.classpath')=='true'}"> <j:set var="tmobile.maven.war.classpath" value="${tmobile.maven.war.classpath} ${dep.artifact}"/> </j:if> </j:forEach> " AND <ant:attribute name="Class-Path" value="${tmobile.maven.war.classpath}"/> --------------------------------------------------------------------- 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]
