[
https://issues.apache.org/jira/browse/SLING-13205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michał Wędzik updated SLING-13205:
----------------------------------
Description: There is a need to write a validator to detect and log the
problem reported in the linked ticket SLING-12474 (was: When processing
bundle with Sling initial content, the conversion process generates:
- a content package with regular files
- repoinit statements ensuring the ancestors are created with the correct JCR
primary type
The primary type for the repoinit statements is looked up in the content
packages.
When a bundle is embedded twice ( in my case two content packages, but it
remains to be seen if this is a requirement ) the generated content package is
processed only once. This happens because the tracking is done by repository
path, not by package id.
This means that any repoinit statements generated for one of the packages will
not make use of the repository path information, leading to incorrect repoinit
statements.)
> Writing a validator to detect incorrect RepoInit statements
> -----------------------------------------------------------
>
> Key: SLING-13205
> URL: https://issues.apache.org/jira/browse/SLING-13205
> Project: Sling
> Issue Type: Improvement
> Components: Content-Package to Feature Model Converter
> Reporter: Michał Wędzik
> Assignee: Robert Munteanu
> Priority: Major
>
> There is a need to write a validator to detect and log the problem reported
> in the linked ticket SLING-12474
--
This message was sent by Atlassian Jira
(v8.20.10#820010)