You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Luca Burgazzoli (JIRA)" <ji...@apache.org> on 2016/07/29 12:52:20 UTC
[jira] [Created] (KARAF-4640) Support startLevel in startup
bundle/features for kustom karaf distribution
Luca Burgazzoli created KARAF-4640:
--------------------------------------
Summary: Support startLevel in startup bundle/features for kustom karaf distribution
Key: KARAF-4640
URL: https://issues.apache.org/jira/browse/KARAF-4640
Project: Karaf
Issue Type: Improvement
Components: karaf-tooling
Reporter: Luca Burgazzoli
When used to generate a custom distribution, the karaf-maven-plugin place all the bundles configured in startupBundles section at the same start level which could cause issues if the startup order matters (i.e. a blueprint extension is required) so it would be nice if the startup level could be configured directly from the plugin to avoid writing a custom feature, something like:
{code:xml}
<configuration>
<startupBundles>
<bundle start-level="60">mvn:my/bundle-1/version</bundle>
<bundle start-level="80">mvn:my/bundle-2/version</bundle>
</startupBundles>
</configuration>
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)