[jira] [Resolved] (SLING-5337) Extract Startup API from Launchpad API

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

     [ https://issues.apache.org/jira/browse/SLING-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oliver Lietz resolved SLING-5337.
---------------------------------
    Resolution: Won't Fix

see [discussion on dev@|http://mail-archives.apache.org/mod_mbox/sling-dev/201512.mbox/%3cCAEWfVJn6nJsiE03MD8+fz2irX3ONVeocLNLEM-b-Tp9-JOo4_w@mail.gmail.com%3e]

> Extract Startup API from Launchpad API
> --------------------------------------
>
>                 Key: SLING-5337
>                 URL: https://issues.apache.org/jira/browse/SLING-5337
>             Project: Sling
>          Issue Type: Improvement
>          Components: Launchpad
>    Affects Versions: Launchpad API 1.2.0
>            Reporter: Oliver Lietz
>            Assignee: Oliver Lietz
>             Fix For: Launchpad API 1.3.0, Startup API 1.0.0
>
>
> {{StartupHandler}}, {{StartupListener}}, {{StartupMode}} and {{StartupService}} in {{org.apache.sling.launchpad.api}} should be moved to {{org.apache.sling.startup.api}} (keeping extending but deprecated classes there for backward compatibility) to decouple Startup from Launchpad.
> A Startup implementation in Sling needs to be provided by every launcher (Launchpad, Crankstart, Karaf)\[1\] whereas {{LaunchpadContentProvider}} is only useful in contexts of Sling's own launcher Launchpad for installation purpose.
> [~cziegeler], [~bdelacretaz]: anything from your POVs to consider?
> \[1\] We discussed to make Startup optional in {{Settings}} but that won't work as we have modules which rely already on it (e.g. {{discovery}}).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)