Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Thu, 13 Oct 2011 12:03:11 +0000 (UTC)
From: =?utf-8?Q?Jean-Baptiste_Onofr=C3=A9_=28Commented=29_=28JIRA=29?=
 <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: 
 <1457537657.8733.1318507391844.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <423147582.8533.1318500791825.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (KARAF-935) Deployer bundles do not start
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/KARAF-935?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13126=
503#comment-13126503 ]=20

Jean-Baptiste Onofr=C3=A9 commented on KARAF-935:
--------------------------------------------

Not only the blueprint deployer is affected, several bundles are in the sam=
e situation.

The issue is that the startup.properties file generated by the karaf-maven-=
plugin is not complete. I'm gonna check the standard feature (for the start=
=3D"true" attribute on the bundle).
               =20
> Deployer bundles do not start
> -----------------------------
>
>                 Key: KARAF-935
>                 URL: https://issues.apache.org/jira/browse/KARAF-935
>             Project: Karaf
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: Ioannis Canellos
>            Assignee: Ioannis Canellos
>
> The deployer bundles, does not start on 3.0.0-SNAPSHOT.
> It seems that they all have as private package org.apache.karaf.util, whi=
ch in version 3.0.0-SNAPSHOT causes the import of org.apache.felix.service.=
command.
> I think we need to set provisional status on that package, as happens to =
the rest of the bundles (e.g. org.apache.features.core).
> I am not sure what the purpose of this property is, but the bundles won't=
 start without it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira