felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard S. Hall (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-5049) Resolver does not choose the revision with the lowest bundle ID
Date Tue, 06 Oct 2015 14:32:26 GMT

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

Richard S. Hall commented on FELIX-5049:

I don't think this is a good idea. I understand what you are trying to achieve, but I'm not
sure the best way to achieve it. First of all, such a heuristic would lead to sorting results
that varied over time and could become inconsistent dynamically.

Secondly, even if you wanted to ignore the potential inconsistencies, it is still not clear
the heuristic makes sense, since it only takes into account services registered directly by
the package provider, but it is possible that there is an importer of the package that is
providing the service too. This makes the heuristic mostly meaningless since it is just stabbing
in the dark. And, of course, you really wouldn't want to take importers who provide into account
because that would just exacerbate the first issue.

Unfortunately, there is no good solution to this case, I don't think.

> Resolver does not choose the revision with the lowest bundle ID
> ---------------------------------------------------------------
>                 Key: FELIX-5049
>                 URL: https://issues.apache.org/jira/browse/FELIX-5049
>             Project: Felix
>          Issue Type: Bug
>          Components: Resolver
>    Affects Versions: framework-5.2.0
>            Reporter: David Bosschaert
>            Assignee: David Bosschaert
>         Attachments: felix-5049.diff
> The Felix Resolver does not pick the exporting bundle with the lowest bundle ID when
multiple bundles export the same package. This causes [ARIES-1398|https://issues.apache.org/jira/browse/ARIES-1398].
For steps on how to reproduce see that issue.

This message was sent by Atlassian JIRA

View raw message