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/06/11 15:43:00 UTC
[jira] [Resolved] (SLING-8423) Make Provisioning to Feature Model
Usable for Sling Conversion
[ https://issues.apache.org/jira/browse/SLING-8423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Schaefer resolved SLING-8423.
-------------------------------------
Resolution: Fixed
> Make Provisioning to Feature Model Usable for Sling Conversion
> --------------------------------------------------------------
>
> Key: SLING-8423
> URL: https://issues.apache.org/jira/browse/SLING-8423
> Project: Sling
> Issue Type: Improvement
> Components: Feature Model
> Affects Versions: Feature Model Converter 1.0.2
> Reporter: Andreas Schaefer
> Assignee: Andreas Schaefer
> Priority: Major
> Fix For: Feature Model Converter 1.0.4
>
>
> I am using the Sling Feature Model Converter to convert Sling’s Provisioning Model from the Launchpad Starter into a Feature Model to run Sling with the Feature Launcher. There are several issues with it and I want to tackle them to create the FM without any manual interactions:
> 1. Make it an executable application like the Content Package to Feature Model Converter using the piccocli
> 2. Make the Model Id configurable so that it fits into Sling Feature Maven Plugin by being able to set group, artifact, classifier and version add at the 'slingosgifeature' type
> 3. Enable to drop duplicate properties like in our case the 'provisioning.model.name’
> 4. Replace variables in the bundle id with the actual value if that is still an issue
> 5. Make sure ‘repoinit’ is of type TEXT and not JSON
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)