[
https://issues.apache.org/jira/browse/SLING-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-4728.
----------------------------------------
Resolution: Fixed
At revision 1684884 I have moved the new crankstart launcher from my
whiteboard back under sling/contrib/crankstart.
All the tests pass as with the old version before using the provisioning model,
except for the ones that used crankstart command extensions which do not have
an equivalent in the provisioning model (and are probably not needed anyway).
I have moved the old crankstart in my whiteboard just in case we need to
salvage something else from it, at
https://svn.apache.org/repos/asf/sling/whiteboard/bdelacretaz/crankstart-before-provisioning-model/
I'll add some docs at
http://sling.apache.org/documentation/development/slingstart.html
Marking this ticket fixed, we'll create more specific ones if needed.
> Crankstart should use the Sling Provisioning Model
> --------------------------------------------------
>
> Key: SLING-4728
> URL: https://issues.apache.org/jira/browse/SLING-4728
> Project: Sling
> Issue Type: Improvement
> Components: Crankstart
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
>
> Crankstart should be converted to use the Sling Provisioning Model that was
> created in the meantime.
> This should preserve the following features:
> Set Initial classpath, select framework version
> Set defaults for variables, override with system properties
> Set OSGi framework properties, with variable
> Install configs early, as soon as ConfigAdmin is available
> OSGi configs with typed values
> Guard against multiple factory config creation (CRANKSTART_CONFIG_ID)
> Ability to register new startup commands
> mvn:protocol is optional, can also use http
> log messages during startup
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
