You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Wolfgang Glas (JIRA)" <ji...@apache.org> on 2010/08/31 13:36:54 UTC

[jira] Commented: (KARAF-179) Upgrade to felix framework 3.0.2

    [ https://issues.apache.org/jira/browse/KARAF-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904604#action_12904604 ] 

Wolfgang Glas commented on KARAF-179:
-------------------------------------

Hi Jean-Baptiste,

Thanks a lot for your clarification , sorry for bothering you with a duplicate issue.

So I'm looking forward to the next karaf release ;-)

  Wolfgang  

> Upgrade to felix framework 3.0.2
> --------------------------------
>
>                 Key: KARAF-179
>                 URL: https://issues.apache.org/jira/browse/KARAF-179
>             Project: Karaf
>          Issue Type: Improvement
>          Components: runtime
>    Affects Versions: 2.0.0
>            Reporter: Wolfgang Glas
>            Assignee: Jean-Baptiste Onofré
>
> Please upgrade to felix 3.0.2, because it fixes a rather nasty problem during the classpath resolution of a bundle. felix-3.0.1 does not show the root cause of aclass resolution problems, which has been fixed in felix-3.0.2.
> If I have a bundle, which imports it's own package and this imported package has a missing dependency, I have to use the debugger to find out about such indirectly missing packages. felix-3.02 would improve this situation dramatically show ing the whole dependency path leading up to the resolution problem.
> TIA for fixing and best regards,
>    Wolfgang

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.