[jira] [Commented] (SLING-8626) Content Package Converter is taking Group from Package Group instead of from Maven Group

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (SLING-8626) Content Package Converter is taking Group from Package Group instead of from Maven Group

Oliver Lietz (Jira)

    [ https://issues.apache.org/jira/browse/SLING-8626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16904890#comment-16904890 ]

Konrad Windszus commented on SLING-8626:
----------------------------------------

Newer versions of the Maven Plugin for content-packages write the Maven group and artifactact id to the properties.xml in dedicated properties: groupId and artifactId (https://jackrabbit.apache.org/filevault/properties.html).

> 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
>            Priority: Major
>
> 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)