[jira] Commented: (MPWAR-23) Plugin doesn't allow to construct Class-Path section of manifest

[ji...@codehaus.org]

The following comment has been added to this issue:

     Author: dion gillard
    Created: Tue, 30 Mar 2004 11:47 PM
       Body:
I've just finished doing MPWAR-22 (which allows you to specify the MANIFEST in an external file like the jar plugin), and this seems like a handy addition.

Could you update the war plugin with a test for your patch?
---------------------------------------------------------------------
View this comment:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPWAR-23&page=comments#action_18025

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPWAR-23

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MPWAR-23
    Summary: Plugin  doesn't allow to construct Class-Path section of manifest
       Type: Bug

     Status: Open
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven-war-plugin

   Assignee: Jason van Zyl
   Reporter: Michal Szklanowski

    Created: Tue, 30 Mar 2004 4:30 AM
    Updated: Tue, 30 Mar 2004 11:47 PM

Description:
I would like to have Class-Path section of my WAR manifest pointing to dependent JARS - because my WAR is embedded in EAR and I don't want to duplicate jars by copying them into WEB-INF/lib.

I just want dependent jars to exist in root directory of EAR module so WAR can make use of them.

But it is impossible to set Class-Path for WAR.

I patched WAR plugin and inserted the following code snippet:

    <j:forEach var="dep" items="${pom.dependencies}">
      <j:if test="${dep.getProperty('war.manifest.classpath')=='true'}">
        <j:set var="maven.war.manifest.classpath" value="${maven.war.manifest.classpath} ${dep.artifact}"/>
      </j:if>
    </j:forEach>

      <ant:manifest>
        ...
        <ant:attribute name="Class-Path" value="${maven.war.manifest.classpath}"/>


So I iterate over dependencies and include in war.manifest.classpath those, who have property war.manifest.classpath set to true.

I want to make request to get rid of manual patching of WAR plugin because I think it is unlikely to be good way of solving such problems.


---------------------------------------------------------------------
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org