[
https://issues.apache.org/jira/browse/SLING-10031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17257085#comment-17257085
]
Eric Norman commented on SLING-10031:
-------------------------------------
[~olli] It looks like the consumer bundles that import and use stuff from the
{{org.apache.sling.api.request }}package are probably getting a too specific
range for the import package version?
Specifically, the import-package item ends up as: org.apache.sling.api.request;
version="[2.4, 2.5)" for the following bundles which leads to troubles running
the automated tests in the servlets.resolver project since the new "2.5.0"
exported package number no longer satisfies that range:
# org.apache.sling.jcr.jackrabbit.usermanager
# org.apache.sling.scripting.sightly
# org.apache.sling.servlets.resolver
I'm assuming this has something to do with bndlib choosing the
"provider-policy" instead of the "consumer-policy" when calculating the version
ranges?
>From what I read, the default definitions are:
{code:java}
-consumer-policy ${range;[==,+)}
-provider-policy ${range;[==,=+)}
{code}
I'm not sure what the best solution is here. Should the ConsumerType and
ProviderType annotated classes be in different packages to account for how the
import version policy of bnd treats those? Or should the consumers supply a
custom import package macro like the following to override the default behavior?
{code:java}
org.apache.sling.api.request; version="${range;[==,+)}"{code}
Or maybe some other solution that I haven't thought of?
> 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)