[
https://issues.apache.org/jira/browse/SLING-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308813#comment-17308813
]
Stefan Seifert commented on SLING-10243:
----------------------------------------
i think a good deal of code what is needed to implement this here could be
taken over from this maven plugin (see [this
article|https://wcm-io.atlassian.net/l/c/RjW85bye] about the background):
https://wcm.io/tooling/maven/plugins/sling-initial-content-transform-maven-plugin/
https://github.com/wcm-io/wcm-io-tooling/tree/develop/maven/plugins/sling-initial-content-transform-maven-plugin
> Extract Sling-Initial-Content from bundles and put into dedicated packages
> --------------------------------------------------------------------------
>
> Key: SLING-10243
> URL: https://issues.apache.org/jira/browse/SLING-10243
> Project: Sling
> Issue Type: Improvement
> Components: Content-Package to Feature Model Converter
> Reporter: Konrad Windszus
> Priority: Major
>
> As described in
> https://lists.apache.org/thread.html/r1162d545922381187a0530f838b684b60f2a8ea28a12649ae79372e8%40%3Cdev.sling.apache.org%3E
> Sling-Initial-Content leads to ERRORs when used with Oak Composite Node
> Store, as those are evaluated during each bundle start. At times when that
> part of the repo is read-only an ERROR is logged.
> The following steps are necessary:
> # Check manifest from bundle for header {{Sling-Initial-Content}}
> # For all entry paths in the header split up by mutable/immutable and create
> a content package for each category
> # Modify manifest to no longer include {{Sling-Initial-Content}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
