Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Thu, 7 Jul 2011 08:58:17 +0000 (UTC)
From: "Jamie goodyear (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: 
 <1339960197.6730.1310029097636.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <917005527.12152.1301082665804.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Closed] (KARAF-534) Startlevel: Strange deployment
 behaviour
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jamie goodyear closed KARAF-534.
--------------------------------


Fixed in the 2.2.1 release.

> 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
>            Assignee: Guillaume Nodet
>            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