felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Bosschaert (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-4525) Refactor the Framework to use the Resolver module
Date Fri, 18 Jul 2014 10:07:04 GMT

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

David Bosschaert commented on FELIX-4525:

I have made a first attempt at this, which can be found here:

It's not finished yet, but I want to make sure I'm going in the right direction with this
before polishing it.
I left 2 line notes (just search for 'note' on the github commit page above) with two questions.

The Felix unit tests all pass with this, but the OSGi CT has a number of failures that still
need to be looked at. I see that many of those relate to the dynamic imports, so Richard I
would be interested in your idea there :)

> Refactor the Framework to use the Resolver module
> -------------------------------------------------
>                 Key: FELIX-4525
>                 URL: https://issues.apache.org/jira/browse/FELIX-4525
>             Project: Felix
>          Issue Type: Task
>          Components: Framework
>    Affects Versions: framework-4.4.0
>            Reporter: David Bosschaert
>            Assignee: David Bosschaert
>             Fix For: framework-4.6.0
> Currently both the framework has a resolver implementation as well as the resolver module,
which has a separate resolver implementation. The resolver module originates from the framework,
but they are not the same any more.
> It would be good to refactor the framework to use the resolver implementation from the
resolver module so that there is no code duplication any more.

This message was sent by Atlassian JIRA

View raw message