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 2020/01/30 17:03:00 UTC
[jira] [Resolved] (SLING-9041) Converter adding .config ending of
sling:OsgiConfig nodes to pid
[ https://issues.apache.org/jira/browse/SLING-9041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Pauls resolved SLING-9041.
-------------------------------
Fix Version/s: Content-Package to Feature Model Converter 1.0.8
Resolution: Fixed
Thanks [~dsuess], its merged.
> Converter adding .config ending of sling:OsgiConfig nodes to pid
> ----------------------------------------------------------------
>
> Key: SLING-9041
> URL: https://issues.apache.org/jira/browse/SLING-9041
> Project: Sling
> Issue Type: Bug
> Components: Content-Package to Feature Model Converter
> Affects Versions: Content-Package to Feature Model Converter 1.0.6
> Reporter: Dominik Süß
> Assignee: Karl Pauls
> Priority: Major
> Fix For: Content-Package to Feature Model Converter 1.0.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The extraction logic of the cp2featuremodel converter currently extracts the pid from the name by stripping of the extension after (including) the last dot - this is wrong in context of sling:OsgiConfig nodes as those are serialized as .xml while the nodes themselves have a .config option. The mechanism should be replaced by an adjustment of the already existing pattern-matcher based logic (currently used for detecting the runmodes).
> As consumers may already depend on nodes without the .config ending the endings .config.xml and .xml must be supported in a non-greedy way (if ending with .config.xml the .config shouldn't be part of the capturing group) for backwards compatiblity.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)