[jira] [Commented] (SLING-3529) Move startup handling to a separate bundle

["Oliver Lietz (JIRA)" <ji...@apache.org>]

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

Oliver Lietz commented on SLING-3529:
-------------------------------------

I don't think that Sling should mess around with start levels in a container like Karaf (in which probably other applications run besides Sling).

And in general I would like to see removing [demand on start levels|http://wiki.osgi.org/wiki/Avoid_Start_Order_Dependencies] and use [Provide-Capability|http://wiki.osgi.org/wiki/Provide-Capability]/[Require-Capability|http://wiki.osgi.org/wiki/Require-Capability] instead.

> Move startup handling to a separate bundle
> ------------------------------------------
>
>                 Key: SLING-3529
>                 URL: https://issues.apache.org/jira/browse/SLING-3529
>             Project: Sling
>          Issue Type: New Feature
>          Components: Launchpad
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Launchpad Base 2.5.2
>
>
> The startup handler is currently embedded in the Sling launchpad base - which makes it impossible to use when Sling is installed in another container like e.g. Apache Karaf.
> We should move this to a separate bundle to make it more reusable



--
This message was sent by Atlassian JIRA
(v6.2#6252)