You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Meng (JIRA)" <ji...@codehaus.org> on 2008/08/21 22:08:27 UTC
[jira] Created: (MWAR-166) exclude the transitive dependency
exclude the transitive dependency
---------------------------------
Key: MWAR-166
URL: http://jira.codehaus.org/browse/MWAR-166
Project: Maven 2.x War Plugin
Issue Type: New Feature
Affects Versions: 2.1
Reporter: Michael Meng
Priority: Blocker
Would you please add a flag which will allow user to have a flexibility to include/exclude the transitive dependent jars in the WEB-INF/lib folder?
The <optional>true</optional> defined inthe dependency is working as desired.
if we have a war project which depends on A.jar and A.jar transitively depends on B.jar (B.jar is not defined in pom.xml). currently the A.jar and B.jar are both included in the lib folder.
If we define A.jar as <optional>true</optional>, then A.jar is exclude from lib folder, but B.jar are included.
What we really want is A.jar to be in lib and B.jar not to be include.
Thanks
--
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
[jira] Updated: (MWAR-166) exclude the transitive dependency
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MWAR-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephane Nicoll updated MWAR-166:
---------------------------------
Priority: Critical (was: Blocker)
> exclude the transitive dependency
> ---------------------------------
>
> Key: MWAR-166
> URL: http://jira.codehaus.org/browse/MWAR-166
> Project: Maven 2.x War Plugin
> Issue Type: New Feature
> Affects Versions: 2.1
> Reporter: Michael Meng
> Priority: Critical
>
> Would you please add a flag which will allow user to have a flexibility to include/exclude the transitive dependent jars in the WEB-INF/lib folder?
> The <optional>true</optional> defined inthe dependency is working as desired.
> if we have a war project which depends on A.jar and A.jar transitively depends on B.jar (B.jar is not defined in pom.xml). currently the A.jar and B.jar are both included in the lib folder.
> If we define A.jar as <optional>true</optional>, then A.jar is exclude from lib folder, but B.jar are included.
> What we really want is A.jar to be in lib and B.jar not to be include.
> Thanks
--
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
[jira] Reopened: (MWAR-166) exclude the transitive dependency
Posted by "Michael Meng (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MWAR-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Meng reopened MWAR-166:
-------------------------------
I use the latest version already (2.1-alpha-2), May be I misunderstood the <optional> usage. Here is what I want --
In the project pom.xml, we define
<dependency>
<groupId>ubhsc</groupId>
<artifactId>service</artifactId>
<!--version>2.5.1</version-->
<optional>true</optional>
</dependency>
and the service-2.5.1.jar are depends on serviceSub-2.6.1.jar (transitive)
It ends up adding the serviceSub-2.6.1.jar to WEB-INF/lib folder and not adding service-2.5.1.jar to the WEB-INF/lib folder.
Here what I really need is add service-2.5.1.jar to the WEB-INF/lib folder, but exclude the serviceSub-2.6.1.jar from the WEB-INF/lib folder.
How to achieve this without using overlay or exclude.... ?
Thanks
> exclude the transitive dependency
> ---------------------------------
>
> Key: MWAR-166
> URL: http://jira.codehaus.org/browse/MWAR-166
> Project: Maven 2.x War Plugin
> Issue Type: New Feature
> Affects Versions: 2.1
> Reporter: Michael Meng
> Assignee: Stephane Nicoll
> Priority: Critical
>
> Would you please add a flag which will allow user to have a flexibility to include/exclude the transitive dependent jars in the WEB-INF/lib folder?
> The <optional>true</optional> defined inthe dependency is working as desired.
> if we have a war project which depends on A.jar and A.jar transitively depends on B.jar (B.jar is not defined in pom.xml). currently the A.jar and B.jar are both included in the lib folder.
> If we define A.jar as <optional>true</optional>, then A.jar is exclude from lib folder, but B.jar are included.
> What we really want is A.jar to be in lib and B.jar not to be include.
> Thanks
--
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
[jira] Closed: (MWAR-166) exclude the transitive dependency
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MWAR-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephane Nicoll closed MWAR-166.
--------------------------------
Assignee: Stephane Nicoll
Resolution: Won't Fix
It's not something that you need to manage in plugins. Use excludes section if you want to exclude a dependency.
Note that optional works as expected in the latest release
> exclude the transitive dependency
> ---------------------------------
>
> Key: MWAR-166
> URL: http://jira.codehaus.org/browse/MWAR-166
> Project: Maven 2.x War Plugin
> Issue Type: New Feature
> Affects Versions: 2.1
> Reporter: Michael Meng
> Assignee: Stephane Nicoll
> Priority: Critical
>
> Would you please add a flag which will allow user to have a flexibility to include/exclude the transitive dependent jars in the WEB-INF/lib folder?
> The <optional>true</optional> defined inthe dependency is working as desired.
> if we have a war project which depends on A.jar and A.jar transitively depends on B.jar (B.jar is not defined in pom.xml). currently the A.jar and B.jar are both included in the lib folder.
> If we define A.jar as <optional>true</optional>, then A.jar is exclude from lib folder, but B.jar are included.
> What we really want is A.jar to be in lib and B.jar not to be include.
> Thanks
--
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
[jira] Closed: (MWAR-166) exclude the transitive dependency
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MWAR-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephane Nicoll closed MWAR-166.
--------------------------------
Resolution: Won't Fix
> exclude the transitive dependency
> ---------------------------------
>
> Key: MWAR-166
> URL: http://jira.codehaus.org/browse/MWAR-166
> Project: Maven 2.x War Plugin
> Issue Type: New Feature
> Affects Versions: 2.1-beta-1
> Reporter: Michael Meng
> Assignee: Stephane Nicoll
> Priority: Critical
>
> Would you please add a flag which will allow user to have a flexibility to include/exclude the transitive dependent jars in the WEB-INF/lib folder?
> The <optional>true</optional> defined inthe dependency is working as desired.
> if we have a war project which depends on A.jar and A.jar transitively depends on B.jar (B.jar is not defined in pom.xml). currently the A.jar and B.jar are both included in the lib folder.
> If we define A.jar as <optional>true</optional>, then A.jar is exclude from lib folder, but B.jar are included.
> What we really want is A.jar to be in lib and B.jar not to be include.
> Thanks
--
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