felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gert Vanthienen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-1914) Add a development subshell to ease troubleshooting classloading/resolution issues
Date Fri, 04 Dec 2009 15:54:20 GMT

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

Gert Vanthienen commented on FELIX-1914:

Added a *{{dev:show-tree}}* in http://svn.apache.org/viewvc?view=revision&revision=887233

This can be used to represent bundle dependencies 'graphically' and it will also warn users
if multiple bundles in the dependency graph are exporting the same packages.

karaf@root> dev:show-tree 36
Bundle wip.foobar [36] is currently INSTALLED
- using wip.bar2 [34] to resolve import org.wip.bar;version="2.0.0"
- using wip.foo [35] to resolve import org.wip.foo

wip.foobar [36]
+- wip.bar2 [34]
+- wip.foo [35]
   +- wip.bar1 [33]

WARNING: multiple bundles are exporting package org.wip.bar
- wip.bar1 [33]
- wip.bar2 [34]

> Add a development subshell to ease troubleshooting classloading/resolution issues
> ---------------------------------------------------------------------------------
>                 Key: FELIX-1914
>                 URL: https://issues.apache.org/jira/browse/FELIX-1914
>             Project: Felix
>          Issue Type: Improvement
>          Components: Karaf
>    Affects Versions: karaf-1.2.0
>            Reporter: Gert Vanthienen
>            Assignee: Gert Vanthienen
>             Fix For: karaf-1.4.0
> At development time, people sometimes bump into classloading or bundle resolution issues.
 Proposing to add a subshell with a few development tools that can be used to troubleshoot
these issues:
> - To solve the "unable to resolve due to constraint violation", we could build a tool
that discovers multiple bundles exporting the same package that are needed to resolve the
given bundle to give people a clue which uses-constraints might be involved
> - To solve a CNFE, we could build a tool that takes a snapshot of imports, enabled dynamic
imports and refreshes the bundle and then checks the imported packages again to see which
imports were added by the dynamic import

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

View raw message