You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Oliver Lietz (JIRA)" <ji...@apache.org> on 2015/11/27 11:04:11 UTC
[jira] [Created] (SLING-5338) Provide a configurable Startup API
implementation
Oliver Lietz created SLING-5338:
-----------------------------------
Summary: 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)