[
https://issues.apache.org/jira/browse/SLING-6114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15555349#comment-15555349
]
ASF GitHub Bot commented on SLING-6114:
---------------------------------------
GitHub user stefanseifert opened a pull request:
https://github.com/apache/sling/pull/179
SLING-6114 Support nested configurations in configurated locations
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/stefanseifert/sling
feature/SLING-6114-nested-conf-configs
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/sling/pull/179.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #179
----
commit ecb73376117af30bf99c1c2aff51e00737d8f56b
Author: sseifert <[email protected]>
Date: 2016-10-07T15:00:40Z
SLING-6114 Support nested configurations in configured locations
commit b43fd8daebf5a801007a1df0eec69ceacb4019a9
Author: sseifert <[email protected]>
Date: 2016-10-07T15:12:21Z
SLING-6114 Allow only one single (configurable) path to store
configurations in, and to reference to
----
> Support nested configurations in configurated locations
> -------------------------------------------------------
>
> Key: SLING-6114
> URL: https://issues.apache.org/jira/browse/SLING-6114
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Reporter: Carsten Ziegeler
> Assignee: Stefan Seifert
> Labels: contextaware-config
> Fix For: Context-Aware Configuration 1.0.0
>
>
> Let's assume you have a content like this:
> /content/level1/level2[@sling-config-ref='/conf/project/sub']
> and configurations
> /conf/project/something
> /conf/project/sub/something-else
> the default path strategy should directly go up the hierarchy in the
> configured location (/conf in this case), so /conf/project/sub is tried
> first, then /conf/project and then the other configured paths.
> The only question is if you have
> /libs/conf/project/sub
> is this handled before /conf/project or after?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
