You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/12/18 14:56:19 UTC

[jira] Updated: (MNG-2864) Optional is not transitive

     [ http://jira.codehaus.org/browse/MNG-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MNG-2864:
------------------------------

    Fix Version/s:     (was: Reviewed Pending Version Assignment)
                   3.x

> Optional is not transitive
> --------------------------
>
>                 Key: MNG-2864
>                 URL: http://jira.codehaus.org/browse/MNG-2864
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Dependencies
>            Reporter: Bernhard Mähr
>            Priority: Minor
>             Fix For: 3.x
>
>
> Hello!
> I have this situation:
> WAR
>   |----- compile/optional----> POM ---- compile ---> JAR1
>   |----- compile/optional----> JAR2
> If I build WAR I get a war-file with the Manifest entries JAR1 and JAR2  and the file JAR1 in WEB-INF\lib.
> I would expect a war-file with the Manifest entries JAR1 and JAR2  and no WEB-INF\lib.
> It seams to me that  JAR1 is included because the second dependency is without optional and the optional from the frist dependency is not transitive to the second dependency. 
> Generally I think it is a hack  to use the combination compile/optional to decide a lib should be included in Manifest but not in the lib dir. I think the should be an additional  scope betwen compile and provided for this purpose.
> Bernhard Mähr 

-- 
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira