[jira] [Commented] (SLING-12120) Align Feature Structure with Starter
[ https://issues.apache.org/jira/browse/SLING-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (SLING-12120) Align Feature Structure with Starter
[ https://issues.apache.org/jira/browse/SLING-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779541#comment-17779541 ] Dan Klco commented on SLING-12120: -- That's a really good question [~rombert]. For the moment, I was planning on syncing the directories manually. We could consider a "sling base" type feature aggregate which contains the common configurations and dependencies for a generic sling application. The problem is that with the [ASF release process|https://www.apache.org/legal/release-policy.html#release-approval], we'd either have to go through a full release vote for this _very_ frequently or accept that the base will only be updated when we decide to do a major Sling release. Another option would be to designate certain features / directories as "base" features which would make synchronizing these features easier or potentially even automated by just copying the relevant directories. > 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)
[jira] [Commented] (SLING-12120) Align Feature Structure with Starter
[ https://issues.apache.org/jira/browse/SLING-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779396#comment-17779396 ] Robert Munteanu commented on SLING-12120: - [~dklco] - I'm curious to hear if you have any ideas about keeping the Starter and downstream apps (CMS for instance) in sync, other than manually watching and applying the changes. Version updates might be easy to do with similar renovate configurations, but for structural changes like SLING-12117 I am not sure what can be done. > 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)
