[jira] [Closed] (KARAF-4640) Support startLevel in startup bundle/features for kustom karaf distribution

["Luca Burgazzoli (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KARAF-4640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luca Burgazzoli closed KARAF-4640.
----------------------------------
    Resolution: Not A Bug

It is already supported by bundle attributes:

{code:xml}
<configuration>
  <startupBundles>
    <bundle>mvn:my/bundle-1/version;start-level=70</bundle>
    <bundle>mvn:my/bundle-2/version;start-level=80</bundle>
  </startupBundles>  
</configuration>
{code}


> 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>
>         <uri>mvn:my/bundle-1/version</uri>
>         <startLevel>60</startLevel>
>     </bundle>
>     <bundle>
>         <uri>mvn:my/bundle-2/version</uri>
>         <startLevel>80</startLevel>
>     </bundle>
>   </startupBundles>  
> </configuration>
> {code}
> Or:
> {code:xml}
> <configuration>
>   <startupBundles>
>     <bundle>mvn:my/bundle-1/version@60</bundle>
>     <bundle>mvn:my/bundle-2/version@80</bundle>
>   </startupBundles>  
> </configuration>
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)