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

Jürgen Albert commented on FELIX-6379:
--------------------------------------

The repo can ge found [here|https://gitlab.com/gecko.io/geckoMongoEMF/]. The 
offending bndrun is this 
[one|https://gitlab.com/gecko.io/geckoMongoEMF/-/blob/develop/org.gecko.emf.mongo.bom/required.bndrun].
 If you want to provoke the issue, you need to remove org.gecko.emf.osgi.json 
from the -runblacklist.

> Resolver keeps orphant dependency branches
> ------------------------------------------
>
>                 Key: FELIX-6379
>                 URL: https://issues.apache.org/jira/browse/FELIX-6379
>             Project: Felix
>          Issue Type: Bug
>          Components: Resolver
>         Environment: bnd
>            Reporter: Jürgen Albert
>            Priority: Minor
>         Attachments: resolver.jpg
>
>
> I use the resolver in bnd. Thus this might be an issue of the bnd way of 
> using it, but I will adress it here first.
> It appears that the resolver keeps dependency branches of dependences it once 
> considered variable, but through out at a certain point. 
> I have project that uses mongo. Mongo itself uses bson and the mongo driver 
> bundle brings all the necessary classes with proper exports and imports. The 
> workspace repositories contain however dependencies for our EMF BSON support 
> using bson4jackson and jackson.
> If I resolve with only the mongo related components as requirements, the 
> jackson and bson4jackson dependencies creep in. If I look at the reason (see 
> screenshot), it tells me that `org.gecko.emf.osgi.bson` is the cause. This 
> bundle however is not part of the resolve result. 
>  
> If I actively deny list this bundle (and `org.gecko.emf.osgi.json` for some 
> reason), they don't appear.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to