[
https://issues.apache.org/jira/browse/SLING-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780354#comment-17780354
]
Robert Munteanu commented on SLING-12120:
-----------------------------------------
[~dklco] - yes, syncing manually is what I usually do. I like the idea of
automatically sync'ing (via tooling) certain 'base' features. I have the same
idea for my demo app -
https://github.com/rombert/pospai/tree/master/launcher/src/main/features/platform
. I keep the Starter features under 'platform' and try to keep them manually
in sync.
Where that breaks down a bit is are 'merge conflicts', for instance:
- downstream app removes config
https://github.com/rombert/pospai/blob/b0159452474f237208a5196be83624c3bf2ac475/launcher/src/main/features/platform/scripting.json#L98-L102
that comes from the starter, it's not needed
- starter adds another extension to the list
- reconciling can't be done manually
But maybe that's thinking too far ahead and if we manage to the the features
right consumers can simply copy over and sync the starter features and delete
the ones they don't need.
> Align Feature Structure with Starter
> ------------------------------------
>
> Key: SLING-12120
> URL: https://issues.apache.org/jira/browse/SLING-12120
> Project: Sling
> Issue Type: Improvement
> Components: App CMS
> Affects Versions: App CMS 1.1.6
> Reporter: Dan Klco
> Assignee: Dan Klco
> Priority: Major
> Fix For: App CMS 1.1.8
>
>
> There's a significant delta between the configuration of the CMS app and the
> Sling Starter. Now that the Sling Starter is receiving regular updates, it'd
> be beneficial to align the feature structure in the CMS App with the starter
> to enable easy syncing of updates.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
