[
https://issues.apache.org/jira/browse/SLING-10031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17258750#comment-17258750
]
Carsten Ziegeler commented on SLING-10031:
------------------------------------------
I assume the narrow package range is because of other usages from that package
(and not the newly introduced MediaRangeList which would be a consumer type).
As [~olli] points out, we mixed too many things into the same package. Utility
classes are best put into a separate package, unfortunately we didn't do this
for RequestUtil and ResponseUtil, but at least for new api additions we should
have clearer boundaries. Therefore I think we should put MediaRangeList into a
new package
> Move MediaRangeList from Servlets POST to Sling API
> ---------------------------------------------------
>
> Key: SLING-10031
> URL: https://issues.apache.org/jira/browse/SLING-10031
> Project: Sling
> Issue Type: Task
> Components: API, Servlets
> Reporter: Oliver Lietz
> Assignee: Oliver Lietz
> Priority: Major
> Fix For: API 2.23.2, Servlets POST 2.3.38
>
>
> {{org.apache.sling.servlets.post.impl.helper}} →
> {{org.apache.sling.api.request}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
