[
https://issues.apache.org/jira/browse/SLING-10031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17258455#comment-17258455
]
Oliver Lietz commented on SLING-10031:
--------------------------------------
[~enorman], Usually when having *minor* changes in Sling API we have to adjust
several other bundles. The Sling API bundle is quite large and we mix consumer
and provider types in some packages (therefore adding annotations now does not
help). Only in some areas we have properly split into API and SPI packages.
We could now check for more candidates which fit into {{o.a.s.api.request,}}
switch to SNAPSHOTs and start the release train or move {{MediaRangeList}} into
a sub-package {{o.a.s.api.request.header}}.
[~cziegeler], [~rombert], What's your view? We face this "challenge" regularly
and I guess we should document it somewhere.
> 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)
