[
https://issues.apache.org/jira/browse/SLING-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15465386#comment-15465386
]
ASF GitHub Bot commented on SLING-6035:
---------------------------------------
GitHub user stefanseifert opened a pull request:
https://github.com/apache/sling/pull/165
SLING-6035 ResourceBuilder: Support absolute paths
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/stefanseifert/sling
feature/SLING-6035-resourcebuilder-abspath
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/sling/pull/165.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 #165
----
commit e7b434bf30840b4c2236a8cf871aea12f3d8becd
Author: sseifert <[email protected]>
Date: 2016-09-05T16:40:45Z
SLING-6035 ResourceBuilder: Support absolute paths
----
> ResourceBuilder: Support absolute paths
> ---------------------------------------
>
> Key: SLING-6035
> URL: https://issues.apache.org/jira/browse/SLING-6035
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Priority: Minor
> Fix For: Resource Builder 1.0.0
>
>
> follow-up from discussion in
> [SLING-5356|https://issues.apache.org/jira/browse/SLING-5356?focusedCommentId=15458657#comment-15458657]
> A) why not supporting absolute paths for resource creation?
> example 1:
> {noformat}
> resourceBuilder =
> getService(ResourceBuilder.class).forResolver(resourceResolver);
> resourceBuilder.resource("content/page1", "sling:config-ref",
> "/conf/content/page1");
> {noformat}
> it would be clearer/cleaner to just write /content/page1 to make sure this
> resource starts at the root, and not at an perhaps unknown parent location.
> currently it's completely forbidden to use absoulte paths.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
