[SLING-10243] Extract Sling-Initial-Content from bundles and put into dedicated packages

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Content-Package to Feature Model Converter 1.1.0
• Component/s: Content-Package to Feature Model Converter
• Labels: regression
• Assignee: Konrad Windszus
• Reporter: Konrad Windszus
• Created: 19/Mar/21 12:04
• Updated: 04/May/23 12:47
• Resolved: 29/Apr/21 13:17

Description

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:

1. Check manifest from bundle for header Sling-Initial-Content
2. For all entry paths in the header split up by mutable/immutable and create a content package for each category
3. Modify manifest to no longer include Sling-Initial-Content

Issue Links

• causes: SLING-10770 JcrNamespaceRegistry.registerCnd throws NPE
• causes: SLING-10382 Wrong namespace url for prefix "sling"
• causes: JCRVLT-516 Ease usage of DocViewProperty outside a repository context
• causes: SLING-10297 Expose org.apache.sling.jcr.contentloader.internal.PathEntry as API
• links to: GitHub Pull Request #74