[
https://issues.apache.org/jira/browse/SLING-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz resolved SLING-5338.
---------------------------------
Resolution: Won't Fix
see [discussion on
dev@|http://mail-archives.apache.org/mod_mbox/sling-dev/201512.mbox/%3ccaewfvjn6njsie03md8+fz2irx3onveoclnlem-b-tp9-joo...@mail.gmail.com%3e]
> Provide a configurable Startup API implementation
> -------------------------------------------------
>
> Key: SLING-5338
> URL: https://issues.apache.org/jira/browse/SLING-5338
> Project: Sling
> Issue Type: New Feature
> Components: Launchpad
> Reporter: Oliver Lietz
> Assignee: Oliver Lietz
> Fix For: Startup Configurable 1.0.0
>
>
> Provide a configurable Startup API implementation which is not tied to a
> launcher (Launchpad, Crankstart, Karaf).
> The preconditions for _Startup finished_ (to some extend) and the
> {{StartupMode}} should be configurable for an initial release.
> The current behavior of the Launchpad implementation is not useful for other
> launchers (where applications besides Sling may be present, see SLING-3529).
> Launchpad implementation:
> * _Startup finished_: OSGi framework is up and _all_ bundles are active
> * {{StartupMode.UPDATE}}: a bundle (whether Sling or not) is found with a
> modification date newer timestamp
> * the lifecycle of the OSGi framework and Sling are tightly coupled
> [~cziegeler], [~bdelacretaz]: again, anything from your POVs to consider?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
