You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Andreas Schaefer (JIRA)" <ji...@apache.org> on 2019/08/14 13:42:00 UTC
[jira] [Resolved] (SLING-8626) Content Package Converter is taking
Group from Package Group instead of from Maven Group
[ https://issues.apache.org/jira/browse/SLING-8626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Schaefer resolved SLING-8626.
-------------------------------------
Resolution: Fixed
At the end it turned out that the issue was that group and artifact ids taken from the package properties (META-INF/vault/properties.xml) or Bundle Header can contain spaces and this is fixed now.
> Content Package Converter is taking Group from Package Group instead of from Maven Group
> ----------------------------------------------------------------------------------------
>
> Key: SLING-8626
> URL: https://issues.apache.org/jira/browse/SLING-8626
> Project: Sling
> Issue Type: Bug
> Components: Content-Package to Feature Model Converter
> Environment: Sling 11, Java 8
> Reporter: Andreas Schaefer
> Assignee: Andreas Schaefer
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> There are two issues with the Content Package to Feature Model Converter with respect to groups:
> # If a group is set in the Content Package then this group will be used in the Feature Id as well as for the folder where it is created
> # If anything changes in the Content Package Vault properties then this will not be reflected in the conversion on a Mac (10.14, Mojave). This is because the deflated file remains the same and in my testing the file did not change even though the package did.
> The issue with the group is severe as the original POM file and the 'cp2fm-converted' file are not in the same location causing issues with the launcher at least.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)