[
https://issues.apache.org/jira/browse/KARAF-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225914#comment-13225914
]
Freeman Fang commented on KARAF-1245:
-------------------------------------
Hi JB,
On Karaf 3.0, the blueprint/spring deployer isn't in startup.properties,
they're in deployer feature description, so unless we also pull
blueprint/spring deployer bundles into startup.properties, there's no way we
can guarantee that they get started before features.core bundle.
I'm +1 to put blueprint/spring deployer bundles into startup.properties, it's
easier for end user when they have features which need blueprint/spring url
handler.
Freeman
> 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
