maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christoph Henrici (JIRA)" <j...@codehaus.org>
Subject [jira] (MASSEMBLY-529) Provide a way to exclude optional dependencies of a module from the assembly
Date Wed, 05 Mar 2014 13:27:59 GMT

    [ https://jira.codehaus.org/browse/MASSEMBLY-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=342417#comment-342417
] 

Christoph Henrici commented on MASSEMBLY-529:
---------------------------------------------

" I would even go as far as suggesting than optional dependencies should not get pulled in
per default." 
100% agreed. From my point of view it yields the plugin even useless... optional means as
i understand: a dependency which should NOT be included transitively by default, but only
when explicitly included as Dependency.

> 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 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 was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message