Hi,
I am studying the migration of an application from Karaf 2.4.x to Karaf
4.0.3. I have a strange behavior, probably related to the start-level of a
feature : When the start level is specified at the feature level, the
bundles contained in the feature are started at the default start level.
Is it an expected behavior, or a regression from karaf 2.4 ?
More precisely, when i install the "camel-core" feature, camel-core bundles
are not started at the level "50", but the default container level despite
the following declaration :
<feature name='camel' version='${project.version}' resolver='(obr)'
start-level='50'>
<feature version='${project.version}'>camel-core</feature>
<feature version='${project.version}'>camel-spring</feature>
<feature version='${project.version}'>camel-blueprint</feature>
</feature>
(Yea, start level is a bad practive, but camel need this in order to work
with spring in osgi..)
--
View this message in context:
http://karaf.922171.n3.nabble.com/Karaf-4-0-3-Features-Start-Level-tp4043865.html
Sent from the Karaf - User mailing list archive at Nabble.com.
