maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian (JIRA)" <>
Subject [jira] Created: (MWAR-125) war manifest generation : optional=true not transitive
Date Mon, 15 Oct 2007 20:23:52 GMT
war manifest generation : optional=true not transitive

                 Key: MWAR-125
             Project: Maven 2.x War Plugin
          Issue Type: Bug
            Reporter: Adrian

war  plugins distinguished the jars going to ear file and those going to WEB-INF/lib.

For a jar that's deployed on the ear and not in WEB-INF/ilb, you jus have to put scope=compile
and optional=true:
      <!-- goes in manifest classpath, but not included in WEB-INF/lib -->

The problem is transitive dependencies of bar-jar1 are put in WEB-INF/lib.

For instance :
if artA declares
and artB declares :
then artC is transitively included in artA dependencies  but with optional=false. 

IMHO it should be included with optional=true since artB is optional.

I'll attach a test case ASAP.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message