You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Niek Raaijmakers (Jira)" <ji...@apache.org> on 2021/11/22 08:03:00 UTC
[jira] [Updated] (SLING-10931) CPConverter - Sling initial content - json files should be converted to folders with a content xml in any case to avoid conflicts
[ https://issues.apache.org/jira/browse/SLING-10931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Niek Raaijmakers updated SLING-10931:
-------------------------------------
Description:
In case of converting sling initial content containing JSON files over to xml, currently the cpconverter simply creates a xml file in the same level.
The problem is when there are other files in a directory with the same name to go along the resourceType.
For example we have:
* page.json
* page/body.html
* page/footer.html
The result will be:
* page.xml
* page/body.html
* page/footer.html
Vault doesn't like this approach so much, resulting in stuff like:
* page.dir
* page.xml
* page/.content.xml (with resourceType nt:folder)
* page/body.html
* page/footer.html
The solution lies in simply redirecting the output to .content.xml in a new folder:
* page/.content.xml
* page/body.html
* page/footer.html
Summary: CPConverter - Sling initial content - json files should be converted to folders with a content xml in any case to avoid conflicts (was: CPConverter - Pages should be converted to folders with a content xml in any case to avoid conflicts)
> CPConverter - Sling initial content - json files should be converted to folders with a content xml in any case to avoid conflicts
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: SLING-10931
> URL: https://issues.apache.org/jira/browse/SLING-10931
> Project: Sling
> Issue Type: Bug
> Components: Content-Package to Feature Model Converter
> Affects Versions: Content-Package to Feature Model Converter 1.1.10
> Reporter: Niek Raaijmakers
> Assignee: Niek Raaijmakers
> Priority: Major
> Fix For: Content-Package to Feature Model Converter 1.1.12
>
>
> In case of converting sling initial content containing JSON files over to xml, currently the cpconverter simply creates a xml file in the same level.
> The problem is when there are other files in a directory with the same name to go along the resourceType.
> For example we have:
>
> * page.json
> * page/body.html
> * page/footer.html
>
> The result will be:
> * page.xml
> * page/body.html
> * page/footer.html
>
> Vault doesn't like this approach so much, resulting in stuff like:
> * page.dir
> * page.xml
> * page/.content.xml (with resourceType nt:folder)
> * page/body.html
> * page/footer.html
> The solution lies in simply redirecting the output to .content.xml in a new folder:
> * page/.content.xml
> * page/body.html
> * page/footer.html
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)