You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Angela Schreiber (Jira)" <ji...@apache.org> on 2021/08/03 13:03:00 UTC
[jira] [Updated] (SLING-10699) Incomplete path conversion in
VaultPackageAssembler.toRepositoryPaths
[ https://issues.apache.org/jira/browse/SLING-10699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Angela Schreiber updated SLING-10699:
-------------------------------------
Affects Version/s: Content-Package to Feature Model Converter 1.1.6
> Incomplete path conversion in VaultPackageAssembler.toRepositoryPaths
> ---------------------------------------------------------------------
>
> Key: SLING-10699
> URL: https://issues.apache.org/jira/browse/SLING-10699
> Project: Sling
> Issue Type: Bug
> Components: Content-Package to Feature Model Converter
> Affects Versions: Content-Package to Feature Model Converter 1.1.6
> Reporter: Angela Schreiber
> Priority: Major
> Fix For: Content-Package to Feature Model Converter 1.1.8
>
>
> [~kpauls] while testing a fix for SLING-10692 i noticed that {{VaultPackageAssembler.toRepositoryPaths}} only removes the _/jcr_root_ prefix from the fvault paths but doesn't convert the segments..... so an path that got moved to repo-init like e.g. _/jcr_root/test/_rep_policy.xml_ doesn't get fully converted to _/test/rep:policy.xml_ before adding it to the extra exclude entries.
> and while we take a closer look at it, i am also wondering if there was any negative side effect from the .xml extension.....
--
This message was sent by Atlassian Jira
(v8.3.4#803005)