[
https://issues.apache.org/jira/browse/KARAF-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126503#comment-13126503
]
Jean-Baptiste Onofré commented on KARAF-935:
--------------------------------------------
Not only the blueprint deployer is affected, several bundles are in the same
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="true" attribute on the bundle).
> 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, which
> 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 administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
