[
https://issues.apache.org/jira/browse/SLING-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652428#action_12652428
]
Bertrand Delacretaz commented on SLING-751:
-------------------------------------------
IIUC, with these changes the bundles have to be in folders name
WEB-INF/resources/N where N is the start level.
Wouldn't it be better to name those folders WEB-INF/resources/bundles/N, for
better organization in the resources folder? That doesn't prevent keeping
resources/bundles for the default level, for backwards compatibility.
> 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.
