[
http://jira.codehaus.org/browse/MNG-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112695
]
Stephane Nicoll commented on MNG-3269:
--------------------------------------
Are you happy if I provide a way to build the manifest in a more elegant way?
Declaring the dependency as provided+optional is such as mess ... I was more
thinking of a declarative way of doing this in the war plugin itself, a la
ArtifactItem of the dependency plugin.
WDYT?
> Different builds for ejb-client optional with parent
> ----------------------------------------------------
>
> Key: MNG-3269
> URL: http://jira.codehaus.org/browse/MNG-3269
> Project: Maven 2
> 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 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
