You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jean-Paul GUIGUI (JIRA)" <ji...@codehaus.org> on 2009/03/31 03:04:12 UTC
[jira] Created: (MASSEMBLY-401) Exclude with useTransitiveFiltering
is excluding transitive artifacts which have ancestors in both include and
exclude condition
Exclude with useTransitiveFiltering is excluding transitive artifacts which have ancestors in both include and exclude condition
--------------------------------------------------------------------------------------------------------------------------------
Key: MASSEMBLY-401
URL: http://jira.codehaus.org/browse/MASSEMBLY-401
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2-beta-3
Environment: maven 2.0.9
Java 1.6.0_12
WinXP
Reporter: Jean-Paul GUIGUI
If we have the following dependencies:
A depends of C,D
B depends of C,E
and if I exclude B and useTransitiveFiltering=true into the assembly descriptor, then the dependency C is as well excluded. It supposed to be kept since it is included from the path A as well, not only from B.
--
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: (MASSEMBLY-401) Exclude with useTransitiveFiltering
is excluding transitive artifacts which have ancestors in both include and
exclude condition
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MASSEMBLY-401:
--------------------------------------
Fix Version/s: (was: 2.2)
> Exclude with useTransitiveFiltering is excluding transitive artifacts which have ancestors in both include and exclude condition
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-401
> URL: http://jira.codehaus.org/browse/MASSEMBLY-401
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-3
> Environment: maven 2.0.9
> Java 1.6.0_12
> WinXP
> Reporter: Jean-Paul GUIGUI
> Assignee: John Casey
>
> If we have the following dependencies:
> A depends of C,D
> B depends of C,E
> and if I exclude B and useTransitiveFiltering=true into the assembly descriptor, then the dependency C is as well excluded. It supposed to be kept since it is included from the path A as well, not only from B.
--
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: (MASSEMBLY-401) Exclude with useTransitiveFiltering
is excluding transitive artifacts which have ancestors in both include and
exclude condition
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed MASSEMBLY-401.
--------------------------------
Resolution: Duplicate
Fix Version/s: 2.2-beta-6
Assignee: John Casey
see MASSEMBLY-504
> Exclude with useTransitiveFiltering is excluding transitive artifacts which have ancestors in both include and exclude condition
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-401
> URL: http://jira.codehaus.org/browse/MASSEMBLY-401
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-3
> Environment: maven 2.0.9
> Java 1.6.0_12
> WinXP
> Reporter: Jean-Paul GUIGUI
> Assignee: John Casey
> Fix For: 2.2-beta-6
>
>
> If we have the following dependencies:
> A depends of C,D
> B depends of C,E
> and if I exclude B and useTransitiveFiltering=true into the assembly descriptor, then the dependency C is as well excluded. It supposed to be kept since it is included from the path A as well, not only from B.
--
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