You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2009/01/27 11:19:00 UTC

[jira] Commented: (SLING-751) Support Start Level assignment for bundles contained in the Launchpad package

    [ https://issues.apache.org/jira/browse/SLING-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667636#action_12667636 ] 

Felix Meschberger commented on SLING-751:
-----------------------------------------

Implemented support for resources/bundles/N path in Rev. 738046.

> Support Start Level assignment for bundles contained in the Launchpad package
> -----------------------------------------------------------------------------
>
>                 Key: SLING-751
>                 URL: https://issues.apache.org/jira/browse/SLING-751
>             Project: Sling
>          Issue Type: New Feature
>    Affects Versions: Launchpad Base 2.0.2, Launchpad App 3, Launchpad Webapp 3
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: Launchpad Base 2.0.4
>
>
> Currently the Sling launcher has no support to assign start levels to the bundles installed from the resources/corebundles and resources/bundles locations. To support assigning specific start levels, the folders in the resources folder should be supported to denote requested start levels.
> This way, we can assign different bundles to different start levels. The bundles in corebundles would default to using start level 1, while the bundles in the bundles would default to the default start level defined by the StartLevel service. Likewise bundles in folder 0 (zero) would be assigned that default start level. Folders whose name cannot be parsed as a positive integer will be ignored.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.