[jira] [Commented] (SLING-7870) Adding FSRegistry based Content Deployment Handler Extension

["Dominik Süß (JIRA)" <ji...@apache.org>]

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

Dominik Süß commented on SLING-7870:
------------------------------------

Proposal at https://github.com/DominikSuess/sling-org-apache-sling-feature-content-extension
This depends on SLING-7871

> Adding FSRegistry based Content Deployment Handler Extension
> ------------------------------------------------------------
>
>                 Key: SLING-7870
>                 URL: https://issues.apache.org/jira/browse/SLING-7870
>             Project: Sling
>          Issue Type: Improvement
>          Components: Feature Model
>            Reporter: Dominik Süß
>            Priority: Major
>
> The current WIP of the feature model launcher provides a simplistic artifact handler feeding all artifacts into the Sling OSGi Installer to be processed.
> To get to a more deterministic and layerable content deployment mechanism an extension should be written that satisfies the following requirements:
> * uses [Vault FSRegistry|https://github.com/apache/jackrabbit-filevault/blob/jackrabbit-filevault-3.2.0/vault-core/src/main/java/org/apache/jackrabbit/vault/packaging/registry/impl/FSPackageRegistry.java] for prebuilding of package registry and precalulation of an execution plan 
> * works on top of a prefilled package registry (precaching)
> * supports startorder to separate into separate executionplans that get executed in sequence
> ** this allows to separate off a content base that gets fully installed ahead of any rest which allows prebuilding a precached repository that can be shared as starting point across instances



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)