[
https://issues.apache.org/jira/browse/KARAF-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022640#comment-13022640
]
Jean-Baptiste Onofré commented on KARAF-534:
--------------------------------------------
Achim succeed to reproduce the issue with the following actions:
<anierbeck> to set the version of the webconsole to 1.0.3-SNAPSHOT (it should
be 1.0.2 right now)
<anierbeck> in the standard features xml
<anierbeck> in your runtime
<anierbeck> do features:install web webconsole
<anierbeck> and you'll see that webconsole failed but web is in sl 1 :)
> Startlevel: Strange deployment behaviour
> -----------------------------------------
>
> Key: KARAF-534
> URL: https://issues.apache.org/jira/browse/KARAF-534
> Project: Karaf
> Issue Type: Bug
> Components: runtime
> Affects Versions: 2.2.1, 3.0.0
> Reporter: Achim Nierbeck
> Priority: Critical
> Fix For: 2.2.1, 3.0.0
>
>
> In the 2.2.x branch exists a strange behavior regarding deployment of bundles
> where dependencies are not resolved.
> Scenario:
> Bundle A depends on Bundle B but Bundle B isn't deployed yet.
> Deploy Bundle A by copying it to the deploy folder. The Bundle
> doesn't show up when issuing the list command. If la is used
> the bundle is shown in a Installed state and it is using startlevel 1.
> Now if Bundle B is deployed (even by command on shell) it also
> is using startlevel 1 and therefore isn't listed when using the list command.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
