You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Stephane Nicoll (JIRA)" <ji...@codehaus.org> on 2007/04/12 14:47:46 UTC

[jira] Commented: (MEAR-62) scope "provided" not applied

    [ http://jira.codehaus.org/browse/MEAR-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92707 ] 

Stephane Nicoll commented on MEAR-62:
-------------------------------------

bah weird !

Do you have a test project to reproduce your problem?

> scope "provided" not applied
> ----------------------------
>
>                 Key: MEAR-62
>                 URL: http://jira.codehaus.org/browse/MEAR-62
>             Project: Maven 2.x Ear Plugin
>          Issue Type: Bug
>    Affects Versions: 2.3
>         Environment: Any
>            Reporter: johan Eltes
>
> When packaging an ear, the ear plugin does not exclude transitive dependencies with scope "provided". A war or ejb project may declare "provided"-scoped dependencies (e.g. j2ee apis). The purpose is to not include these dependencies when packaging the archive. For enterprise applications, the EAR project is responsible for doing the packaging of its modules dependencies. Although scope packaging is defined for transitive dependencies (dependencies declared by the module POMs), the ear plug-in still includes these libraries in the produced ear.

-- 
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