You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Carlos Sanchez (JIRA)" <ji...@codehaus.org> on 2005/10/23 05:43:12 UTC
[jira] Updated: (MNG-1280) tag really doesn't work
[ http://jira.codehaus.org/browse/MNG-1280?page=all ]
Carlos Sanchez updated MNG-1280:
--------------------------------
Priority: Critical (was: Major)
Component: maven-war-plugin
> <optional/> tag really doesn't work
> -----------------------------------
>
> Key: MNG-1280
> URL: http://jira.codehaus.org/browse/MNG-1280
> Project: Maven 2
> Type: Bug
> Components: maven-war-plugin
> Versions: 2.0
> Environment: windows
> Reporter: Alexandre Vivien
> Priority: Critical
> Fix For: 2.0.1
> Attachments: 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org