karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jamie goodyear (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KARAF-534) Startlevel: Strange deployment behaviour
Date Thu, 14 Apr 2011 20:41:05 GMT

     [ https://issues.apache.org/jira/browse/KARAF-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jamie goodyear updated KARAF-534:
---------------------------------

    Priority: Critical  (was: Major)

Increasing priority level. 

> 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
>            Reporter: Achim Nierbeck
>            Priority: Critical
>             Fix For: 2.2.1
>
>
> 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

Mime
View raw message