[
https://issues.apache.org/jira/browse/KARAF-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15405449#comment-15405449
]
Ralf Steppacher commented on KARAF-4261:
----------------------------------------
[[email protected]], thanks for your comment and apologies for my long
response times.
Yes, as far as I can tell the problem occurs only when deploying a KAR file via
the {{deploy}} folder. Not being able to use a KAR with the deploy folder will
make the instructions for our operations team for deployment and upgrades that
much more elaborate and error prone. It would be really great of deploying and
undeploying a KAR via the deploy folder could be fixed.
> Bundle start-level seems to be ignored at Karaf restart
> -------------------------------------------------------
>
> Key: KARAF-4261
> URL: https://issues.apache.org/jira/browse/KARAF-4261
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
> Affects Versions: 4.0.3
> Reporter: Ralf Steppacher
> Fix For: 4.1.0, 4.0.6
>
>
> AS a workaround for CAMEL-9483 I have set a start-level for my bundles
> deployed as part of my features. This works as expected during initial
> deployment (order of deployment is according to the start levels I set), but
> not during sub-sequent starts of Karaf. It appears the start-level of the
> bundles is ignored, meaning the order of deployment of my bundles is more or
> less random and I observe the issues described in CAMEL-9483 again.
> {{bundle:list}} shows my bundles with the start-levels they have been
> originally deployed with, though.
> As a workaround I set {{karaf.clean.all = true}} in system.properties.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
