[
https://issues.apache.org/jira/browse/SLING-7140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16213959#comment-16213959
]
Ian Boston commented on SLING-7140:
-----------------------------------
Did you see this commit ?
https://github.com/apache/sling-org-apache-sling-resourceresolver/commit/ec3844be2612f48cb3e599792bc05c36c36cc031
It updates the ResourceResolver so that it doesnt break. The patch passed a
full build of Sling before it was applied, although due to the SVN-Git
migration, it had to be done in multiple commits. I see the Jira only has 1
commit listed so I guess it hasnt been integrated with Git yet.
The reason that it was not in the main commit was that the SVN->Git migration
only moved that bundle and none of the others.
I have no problem if the packages are moved to somewhere else in the Sling API
bundle.
I did open a RTC on sling-dev, but no one replied to it after 24h.
> Support redirects to URLs provided by the underlying datastore.
> ---------------------------------------------------------------
>
> Key: SLING-7140
> URL: https://issues.apache.org/jira/browse/SLING-7140
> Project: Sling
> Issue Type: Bug
> Components: Servlets
> Affects Versions: Servlets Get 2.1.26, JCR Resource 3.0.4
> Reporter: Ian Boston
> Assignee: Ian Boston
> Fix For: Servlets Get 2.1.28, JCR Resource 3.0.6, API 2.16.4,
> Resource Resolver 1.5.32
>
>
> Incorporate changes to allow OAK-6575 to work in Sling,
> Patch available at
> https://github.com/apache/sling/compare/trunk...ieb:OAK-6575-3-2
> Cant me applied until OAK-6575 is released in a version suitable for use in
> Sling.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
