You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Oleg Kalnichevski (JIRA)" <ji...@codehaus.org> on 2010/11/15 12:28:04 UTC
[jira] Created: (MASSEMBLY-529) Provide a way to exclude optional
dependencies of a module from the assembly
Provide a way to exclude optional dependencies of a module from the assembly
----------------------------------------------------------------------------
Key: MASSEMBLY-529
URL: http://jira.codehaus.org/browse/MASSEMBLY-529
Project: Maven 2.x Assembly Plugin
Issue Type: Improvement
Affects Versions: 2.2, 2.2-beta-5
Reporter: Oleg Kalnichevski
Presently optional dependencies of modules in a module set always get pulled in and there appears to be no way to exclude all optional dependencies other than explicitly excluding them one by on
--
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] Commented: (MASSEMBLY-529) Provide a way to exclude optional
dependencies of a module from the assembly
Posted by "Oleg Kalnichevski (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243130#action_243130 ]
Oleg Kalnichevski commented on MASSEMBLY-529:
---------------------------------------------
You can refer to the following project to reproduce the issue
Apache HttpClient project [1] has a caching module [2] which has two optional dependencies (ehcache and memcached). There dependencies are not mandatory and are intended for redistribution with HttpClient.
I was unable to find a straightforward way of excluding those dependencies other than than explicitly excluding each artifact from the dependency set. I would even go as far as suggesting than optional dependencies should not get pulled in per default.
Oleg
[1] http://svn.apache.org/repos/asf/httpcomponents/httpclient/trunk/
[2] http://svn.apache.org/repos/asf/httpcomponents/httpclient/trunk/httpclient-cache/
> Provide a way to exclude optional dependencies of a module from the assembly
> ----------------------------------------------------------------------------
>
> Key: MASSEMBLY-529
> URL: http://jira.codehaus.org/browse/MASSEMBLY-529
> Project: Maven 2.x Assembly Plugin
> Issue Type: Improvement
> Affects Versions: 2.2-beta-5, 2.2
> Reporter: Oleg Kalnichevski
>
> Presently optional dependencies of modules in a module set always get pulled in and there appears to be no way to exclude all optional dependencies other than explicitly excluding them one by on
--
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] Issue Comment Edited: (MASSEMBLY-529) Provide a way to
exclude optional dependencies of a module from the assembly
Posted by "Oleg Kalnichevski (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243130#action_243130 ]
Oleg Kalnichevski edited comment on MASSEMBLY-529 at 11/15/10 5:28 AM:
-----------------------------------------------------------------------
You can refer to the following project to reproduce the issue:
Apache HttpClient project [1] has a caching module [2], which has two optional dependencies (ehcache and memcached). These dependencies are not mandatory and are not intended for redistribution with HttpClient's binary packages.
I was unable to find a straightforward way of excluding those dependencies other than than explicitly excluding each artifact from the dependency set. I would even go as far as suggesting than optional dependencies should not get pulled in per default.
Oleg
[1] http://svn.apache.org/repos/asf/httpcomponents/httpclient/trunk/
[2] http://svn.apache.org/repos/asf/httpcomponents/httpclient/trunk/httpclient-cache/
was (Author: olegk):
You can refer to the following project to reproduce the issue
Apache HttpClient project [1] has a caching module [2] which has two optional dependencies (ehcache and memcached). There dependencies are not mandatory and are intended for redistribution with HttpClient.
I was unable to find a straightforward way of excluding those dependencies other than than explicitly excluding each artifact from the dependency set. I would even go as far as suggesting than optional dependencies should not get pulled in per default.
Oleg
[1] http://svn.apache.org/repos/asf/httpcomponents/httpclient/trunk/
[2] http://svn.apache.org/repos/asf/httpcomponents/httpclient/trunk/httpclient-cache/
> Provide a way to exclude optional dependencies of a module from the assembly
> ----------------------------------------------------------------------------
>
> Key: MASSEMBLY-529
> URL: http://jira.codehaus.org/browse/MASSEMBLY-529
> Project: Maven 2.x Assembly Plugin
> Issue Type: Improvement
> Affects Versions: 2.2-beta-5, 2.2
> Reporter: Oleg Kalnichevski
>
> Presently optional dependencies of modules in a module set always get pulled in and there appears to be no way to exclude all optional dependencies other than explicitly excluding them one by on
--
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] (MASSEMBLY-529) Provide a way to exclude optional
dependencies of a module from the assembly
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MASSEMBLY-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MASSEMBLY-529:
--------------------------------------
Component/s: moduleSet
> Provide a way to exclude optional dependencies of a module from the assembly
> ----------------------------------------------------------------------------
>
> Key: MASSEMBLY-529
> URL: https://jira.codehaus.org/browse/MASSEMBLY-529
> Project: Maven 2.x Assembly Plugin
> Issue Type: Improvement
> Components: moduleSet
> Affects Versions: 2.2-beta-5, 2.2
> Reporter: Oleg Kalnichevski
>
> Presently optional dependencies of modules in a module set always get pulled in and there appears to be no way to exclude all optional dependencies other than explicitly excluding them one by on
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira