maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephane Nicoll (JIRA)" <>
Subject [jira] Updated: (MWAR-114) Different builds for ejb-client optional with parent
Date Sun, 28 Oct 2007 10:50:04 GMT


Stephane Nicoll updated MWAR-114:

    Affects Version/s:     (was: 2.1)
        Fix Version/s: 2.1-alpha-2

Hi Tim,

Thanks for the extensive info. I'm flagging this one as to be fixed for the next alpha. I
think that your patch is a bit weird so I'll investigate how it can be improved.

> Different builds for ejb-client optional with parent
> ----------------------------------------------------
>                 Key: MWAR-114
>                 URL:
>             Project: Maven 2.x War Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1-alpha-1
>            Reporter: Tim Reilly
>             Fix For: 2.1-alpha-2
>         Attachments: MWAR114-maven-war-plugin-2.0.2.patch, MWAR114-maven-war-plugin-2.0.2.patch,
> 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:
For more information on JIRA, see:


View raw message