[ http://jira.codehaus.org/browse/MWAR-2?page=all ]
Maria Odea Ching moved MNG-1280 to MWAR-2:
------------------------------------------
Version: (was: 2.0)
Component: (was: maven-war-plugin)
Workflow: jira (was: Maven)
Key: MWAR-2 (was: MNG-1280)
Project: Maven 2.x War Plugin (was: Maven 2)
> <optional/> tag really doesn't work
> -----------------------------------
>
> Key: MWAR-2
> URL: http://jira.codehaus.org/browse/MWAR-2
> Project: Maven 2.x War Plugin
> Type: Bug
> Environment: windows
> Reporter: Alexandre Vivien
> Assignee: Edwin Punzalan
> Priority: Critical
> Attachments: app-webapp.zip, example.zip
>
>
> In my war project I put the displaytag-1.0 dependency wih the scope runtime.
> When I make my war Maven2 include some others dependencies like
> commons-logging, this is normal because these dependencies are declared in
> the repository side displaytag-1.0.pom, but Maven2 also include in my war the
> dependencies which have the <optional/> in the repository displaytag-1.0.pom
> like xwork-1.0.3.
> I have included a example to explain what I mean. Just run mvn package, and
> look at the war created. Compare the jar included into this war with the
> displaytag-1.0.pom, you can find it at this url :
> http://www.ibiblio.org/maven2/displaytag/displaytag/1.0/displaytag-1.0.pom
> So, my question is : Is this normal ? if Yes, I would like a explanation of
> how work <optional/> tag.
> Or Is this a Bug ?
> thanks,
> Alexandre Vivien
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
