[ https://issues.apache.org/jira/browse/SLING-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15029729#comment-15029729 ]
Carsten Ziegeler commented on SLING-5337: ----------------------------------------- [~olli] Recently I thought about extracting the startup API into a separate package as well. I think we should do this, but probably we should not simply make it a 1:1 copy of the launchpad API, but think about other use cases and if we can fit them into the api > 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)