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 2008/12/02 15:46:44 UTC
[jira] Created: (SLING-751) Support Start Level assignment for
bundles contained in the Launchpad package
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 Webapp 3, Launchpad App 3, Launchpad Base 2.0.2
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.
[jira] Closed: (SLING-751) Support Start Level assignment for
bundles contained in the Launchpad package
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed SLING-751.
-----------------------------------
Resolution: Fixed
This has been implemented and it works. Therefore closing this issue
> 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.
[jira] Commented: (SLING-751) Support Start Level assignment for
bundles contained in the Launchpad package
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652398#action_12652398 ]
Felix Meschberger commented on SLING-751:
-----------------------------------------
Committed changes to the BootstrapInstaller and ClassLoaderResourceProvider to support start level assignment based on bundle "location" in the package in Rev. 722482
> 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.
[jira] Commented: (SLING-751) Support Start Level assignment for
bundles contained in the Launchpad package
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (SLING-751) Support Start Level assignment for
bundles contained in the Launchpad package
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (SLING-751) Support Start Level assignment for
bundles contained in the Launchpad package
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667637#action_12667637 ]
Felix Meschberger commented on SLING-751:
-----------------------------------------
Adapted the launchpad/app, launchpad/bundles and launchpad/jcrapp modules to place the bundles in the correct location in Rev. 738048.
> 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.
[jira] Commented: (SLING-751) Support Start Level assignment for
bundles contained in the Launchpad package
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652706#action_12652706 ]
Felix Meschberger commented on SLING-751:
-----------------------------------------
Hmm, looking at it again, you are perfectly right.
> 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.