You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Alexandre Vivien (JIRA)" <ji...@codehaus.org> on 2005/10/22 18:56:11 UTC
[jira] Created: (MNG-1280) tag really doesn't work
<optional/> tag really doesn't work
-----------------------------------
Key: MNG-1280
URL: http://jira.codehaus.org/browse/MNG-1280
Project: Maven 2
Type: Bug
Versions: 2.0
Environment: windows
Reporter: Alexandre Vivien
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
[jira] Closed: (MNG-1280) tag really doesn't work
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1280?page=all ]
Brett Porter closed MNG-1280:
-----------------------------
Resolution: Duplicate
Fix Version: (was: 2.0.1)
> <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
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-1280) tag really doesn't work
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1280?page=all ]
Carlos Sanchez updated MNG-1280:
--------------------------------
Attachment: app-webapp.zip
Simpler test case using commons-logging
When running
mvn clean:clean package -X
you shouldn't get at the end any of
avalon-framework-4.1.3.jar
log4j-1.2.6.jar
logkit-1.0.1.jar
> <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: 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-1280) tag really doesn't work
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MNG-1280) tag really doesn't work
Posted by "Edwin Punzalan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1280?page=all ]
Edwin Punzalan updated MNG-1280:
--------------------------------
Attachment: MNG-1280-maven-war-plugin.patch
patch also includes fix for a TODO (usage of scope handler)
> <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
> Assignee: Edwin Punzalan
> Priority: Critical
> Fix For: 2.0.1
> Attachments: MNG-1280-maven-war-plugin.patch, 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-1280) tag really doesn't work
Posted by "Edwin Punzalan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1280?page=all ]
Edwin Punzalan updated MNG-1280:
--------------------------------
Comment: was deleted
> <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
> Assignee: Edwin Punzalan
> Priority: Critical
> Fix For: 2.0.1
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-1280) tag really doesn't work
Posted by "Edwin Punzalan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1280?page=all ]
Edwin Punzalan updated MNG-1280:
--------------------------------
Attachment: MNG-1280-maven-ear-plugin.patch
> <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
> Assignee: Edwin Punzalan
> Priority: Critical
> Fix For: 2.0.1
> Attachments: MNG-1280-maven-war-plugin.patch, 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org