[ 
https://issues.apache.org/jira/browse/FELIX-6457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17608048#comment-17608048
 ] 

Tuomas Kiviaho commented on FELIX-6457:
---------------------------------------

[~andre.kuehnert] There is no other workaround that using dependency exceptions 
and cherry picking the deeply transitive dependencies that are needed. 

To fix this issue in the plugin itself (again), one must find the a proper way 
of handling the dependency tree which - I'm not entirely why - got removed in 
#FELIX-6073

> Regression after a change in maven-bundle-plugin:4.2.0 related to leaking of 
> transitive dependencies of excluded artifacts
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FELIX-6457
>                 URL: https://issues.apache.org/jira/browse/FELIX-6457
>             Project: Felix
>          Issue Type: Bug
>          Components: Maven Bundle Plugin
>    Affects Versions: maven-bundle-plugin-4.2.0
>            Reporter: Tuomas Kiviaho
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>
> I've been using {{maven-bundle-plugin:4.1.0}} until now and once I bumped 
> version up to 4.2.0 or newer the logic how transitive dependencies were 
> handled from {{maven-bundle-plugin:3.0.0}} onward has reverted from what was 
> fixed in [FELIX-3565|https://issues.apache.org/jira/browse/FELIX-3565]
> The breaking change has happened at 
> [FELIX-6073|https://issues.apache.org/jira/browse/FELIX-6073] when the plugin 
> was bumped up to Maven 3.0.0 when support for dependency tree via 
> {{org.apache.maven.shared.dependency.graph.DependencyNode}} was removed from 
> {{org.apache.felix.bundleplugin.AbstractDependencyFilter}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to