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

Chetan Mehrotra updated SLING-3388:
-----------------------------------

    Description: 
For certain cases we need to change the start level of existing bundles. For 
example to properly solve SLING-3340 we need to move all non log related 
bundles to Start level > 1

Currently the Launchpad bootstrap support custom commands which are executed 
upon system start. For now they are used to uninstall bundles.

On similar like we can have changestartlevel command to change the start level 
of bundle

Refer to http://markmail.org/thread/2b5m7hq22p7b5vq3 for more details


  was:
For certain cases we need to change the start level of existing bundles. For 
example to properly solve SLING-3340 we need to move all non log related 
bundles to Start level > 1

Currently the Launchpad bootstrap support custom commands which are executed 
upon system start. For now they are used to uninstall bundles.

On similar like we can have changestartlevel command to change the start level 
of bundle




> Enable changing of bundle start level in upgrade
> ------------------------------------------------
>
>                 Key: SLING-3388
>                 URL: https://issues.apache.org/jira/browse/SLING-3388
>             Project: Sling
>          Issue Type: Improvement
>          Components: Launchpad
>    Affects Versions: Launchpad Base 2.5.0
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>
> For certain cases we need to change the start level of existing bundles. For 
> example to properly solve SLING-3340 we need to move all non log related 
> bundles to Start level > 1
> Currently the Launchpad bootstrap support custom commands which are executed 
> upon system start. For now they are used to uninstall bundles.
> On similar like we can have changestartlevel command to change the start 
> level of bundle
> Refer to http://markmail.org/thread/2b5m7hq22p7b5vq3 for more details



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to