[
https://issues.apache.org/jira/browse/SLING-10931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472647#comment-17472647
]
Niek Raaijmakers commented on SLING-10931:
------------------------------------------
[~kwin] , I have a question.
I am trying to copy in parent folder .content.xml's with sling:Folder in case
it's not defined on the repository.
For that I am trying to add these with a merge filter. However when creating a
sample package on a project I bump into this validation error:
[https://github.com/apache/jackrabbit-filevault/blob/561aaa092d721963f16b860de955e6d1752a350e/vault-validation/src/main/java/org/apache/jackrabbit/vault/validation/spi/impl/PackageTypeValidator.java#L53]
What is the reason we can't use includes / excludes in APPLICATION packages? If
so we might want to explore other avenues such as repoinit.
Thanks!
> 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)
