[jira] (MNG-3269) Different builds for ejb-client optional with parent

["Paul Benedict (JIRA)" <ji...@codehaus.org>]

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

Paul Benedict updated MNG-3269:
-------------------------------

    Fix Version/s:     (was: Issues to be reviewed for 3.x)

> Different builds for ejb-client optional with parent
> ----------------------------------------------------
>
>                 Key: MNG-3269
>                 URL: https://jira.codehaus.org/browse/MNG-3269
>             Project: Maven
>          Issue Type: Bug
>    Affects Versions: 2.0.7
>            Reporter: Tim Reilly
>         Attachments: MWAR114-maven-war-plugin-2.0.2.patch, MWAR114-maven-war-plugin-2.0.2.patch, MWAR114-maven-war-plugin-2.1-alpha-1.patch, mytime.zip
>
>
> When trying to package a  j2ee project's ejb-client artifact in the ear /lib directory the war plugin's optional attribute is ignored if building from the parent app project. If you build from the parent project you get the ejb-client packaged in the web-inf/lib directory. If you build the ejb, war, and ear independently you get the ejb-client packaged in the ear /lib directory. It seems when run from the parent project the dependency/artifact doesn't have the optional attribute set.
> Perhaps this is b/c the artifact is a project artifact that was attached from the ejb plugin it is not resolved as optional when the dependency is resolved from the war project.
> Attaching Geronimo's mytime sample with modifications to reproduce the behavior.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)