[
https://issues.apache.org/jira/browse/KARAF-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Pieber resolved KARAF-1878.
-----------------------------------
Resolution: Fixed
Committed r1395933
M
assemblies/apache-karaf/src/main/filtered-resources/minimal/org.apache.karaf.features.cfg
M manual/src/main/webapp/users-guide/provisioning.conf
M
features/core/src/main/java/org/apache/karaf/features/internal/FeaturesServiceImpl.java
M
features/core/src/main/resources/OSGI-INF/blueprint/gshell-features.xml
r1395933 = 0d3f714a5ea08a7a36b05f7697039004bb2510a4
(refs/remotes/origin/karaf-2.3.x)
Committed r1395934
M
assemblies/features/framework/src/main/filtered-resources/resources/etc/org.apache.karaf.features.cfg
M manual/src/main/webapp/users-guide/provisioning.conf
M
features/core/src/main/java/org/apache/karaf/features/internal/FeaturesServiceImpl.java
M
features/core/src/main/resources/OSGI-INF/blueprint/blueprint.xml
r1395934 = 5f12c6bb9e37d13dd36a8114f9fa348ce9b36d68 (refs/remotes/origin/trunk)
> Feature bundle start up order by startLvl
> -----------------------------------------
>
> Key: KARAF-1878
> URL: https://issues.apache.org/jira/browse/KARAF-1878
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-feature
> Affects Versions: 2.3.0, 3.0.0.RC1
> Reporter: Andreas Pieber
> Assignee: Andreas Pieber
> Fix For: 2.3.0, 3.0.0.RC1
>
> Attachments: KARAF-1878-master.patch.txt, KARAF-1878-v2.3.x.patch.txt
>
>
> Currently all features are read, all bundles installed and then started in
> the order they had been installed. Basically this is not a bad behavior, but
> independently it would be even better if we would/could sort the bundles by
> their start lvl before kicking them up. The attached patch shows this
> behavior.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
