[jira] [Commented] (SLING-11617) Skip execution plan processing

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

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

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

The current head of the plugin depends on Filevault 3.5.0 - for consumers depending on a lower version  it may be necessary to fork off and release the same changes on an older filevault version (as 3.5.0 and higher contain breaking changes that require consumer adaption).

> Skip execution plan processing 
> -------------------------------
>
>                 Key: SLING-11617
>                 URL: https://issues.apache.org/jira/browse/SLING-11617
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: Feature Model Content Extension 1.0.10
>            Reporter: Dominik Süß
>            Priority: Major
>
> In cases where stable states are launched without application/feature-model changes it would be safe to completely skip the execution-plan execution and generation of config for the packageinitializer.  As a simple approach a flag could be set that still generates the FS PackageRegistry config in case a content-package extension is present but skips over the executionplan generation and configuration.
> This is specifically useful in cases where composite nodestore is being used and the repository (immutable part) is being produced in a predeployment phase.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)