[
https://issues.apache.org/jira/browse/KARAF-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225938#comment-13225938
]
Jean-Baptiste Onofré commented on KARAF-1245:
---------------------------------------------
Even if the blueprint and spring deployers are not in the startup.properties,
they are started after the features core on trunk:
karaf@root> la|grep -i deployer
[ 43] [Active ] [Created ] [ 30] Apache Karaf :: Deployer ::
Blueprint (3.0.0.SNAPSHOT)
[ 44] [Active ] [Created ] [ 30] Apache Karaf :: Deployer ::
Features (3.0.0.SNAPSHOT)
[ 45] [Active ] [Created ] [ 30] Apache Karaf :: Deployer :: Wrap
Non OSGi Jar (3.0.0.SNAPSHOT)
karaf@root> la|grep -i feature
[ 20] [Active ] [Created ] [ 25] Apache Karaf :: Features :: Core
(3.0.0.SNAPSHOT)
I don't think it's required to put the deployers in the startup.properties, but
we should update the start-level to 24 in order to start them before the
features core bundle.
I do it ;)
> blueprint deployer and spring deployer should get started before
> features.core bundle
> -------------------------------------------------------------------------------------
>
> Key: KARAF-1245
> URL: https://issues.apache.org/jira/browse/KARAF-1245
> Project: Karaf
> Issue Type: Improvement
> Reporter: Freeman Fang
> Assignee: Jean-Baptiste Onofré
> Fix For: 2.2.6
>
>
> When org.apache.karaf.features.core bundle is up, it will load features
> descriptors and try install features, however if the features descriptor has
> bundle like
> <bundle>blueprint:file:etc/some-blueprint.xml</bundle>, we need blueprint url
> handler available in the OSGi container, so we need blueprint deployer and
> spring deployer get started before features.core bundle
--
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
