You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2015/05/19 17:32:01 UTC

[jira] [Commented] (SLING-4728) Crankstart should use the Sling Provisioning Model

    [ https://issues.apache.org/jira/browse/SLING-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550620#comment-14550620 ] 

Bertrand Delacretaz commented on SLING-4728:
--------------------------------------------

I have added a provisioning.model command to Crankstart in http://svn.apache.org/r1680316 - this is a first short with many things left in the Crankstart command file that can probably be removed.

> 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)