[
https://issues.apache.org/jira/browse/SLING-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)
