You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Karl Pauls (Jira)" <ji...@apache.org> on 2021/07/02 20:43:00 UTC

[jira] [Resolved] (SLING-10469) Breaking leftover dir folders for configs in generated packages

     [ https://issues.apache.org/jira/browse/SLING-10469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Pauls resolved SLING-10469.
--------------------------------
    Resolution: Fixed

Done in https://github.com/apache/sling-org-apache-sling-feature-cpconverter/pull/96

> Breaking leftover dir folders for configs in generated packages
> ---------------------------------------------------------------
>
>                 Key: SLING-10469
>                 URL: https://issues.apache.org/jira/browse/SLING-10469
>             Project: Sling
>          Issue Type: Bug
>          Components: Content-Package to Feature Model Converter
>    Affects Versions: Content-Package to Feature Model Converter 1.1.4
>            Reporter: Dominik Süß
>            Assignee: Dominik Süß
>            Priority: Major
>
> In case a configuration package is generated from an existing repository due to the serialization logic for each nt:file representing a configuration there is also a .dir folder (with an embedded .content.xml declaring nodetype etc.) as a sibling.
> The configuration handlers only handle the binaries but don't recognize the sibling structures which will make them remain in the package and therefore render the packages invalid as the binary belonging to the nt:file is being stripped out.
> To prevent this (rare but existing) edge case the Configuration handler should also detect the dir folder and drop it from assembly in the target package as well.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)