You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by vladbailescu <gi...@git.apache.org> on 2015/03/09 12:40:25 UTC
[GitHub] sling pull request: SLING-4483 - Sightly: data-sly-resource does n...
GitHub user vladbailescu opened a pull request:
https://github.com/apache/sling/pull/66
SLING-4483 - Sightly: data-sly-resource does not properly resolve relative paths
Prepended current resource path to relative paths to make sure normalization doesn't break the paths. The same approach is used by <sling:include ../>
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vladbailescu/sling SLING-4483-sightly-resource-relative-paths
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/sling/pull/66.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 #66
----
commit 9728f8ae36001c174fa9ae74a9a6ac17e0979df9
Author: vladbailescu <ba...@adobe.com>
Date: 2015-03-09T11:39:34Z
SLING-4483 - Sightly: data-sly-resource does not properly resolve relative paths
Prepended current resource path to relative paths to make sure normalization doesn't break the paths. The same approach is used by <sling:include ../>
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] sling pull request: SLING-4483 - Sightly: data-sly-resource does n...
Posted by vladbailescu <gi...@git.apache.org>.
Github user vladbailescu closed the pull request at:
https://github.com/apache/sling/pull/66
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---