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 Mon, 15 Sep 2014 09:33:34 GMT

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

David Bosschaert commented on FELIX-4525:
-----------------------------------------

Good to hear [~rickhall]! Yes, the dynamic import stuff is the main piece that was still causing
a lot of CT failures, so if you have any thoughts what to do there it would help a lot!

I'll double check the BundleRevisionImpl.toString(). There was a reason why I expanded it....

> 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
(v6.3.4#6332)

Mime
View raw message