[
https://issues.apache.org/jira/browse/SLING-12657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17927090#comment-17927090
]
Robert Munteanu commented on SLING-12657:
-----------------------------------------
The way I understand it, if we import a package and implement a ProviderType
interface then we'll get a narrow import range.
Today the import range is {{org.apache.jackrabbit.api;version="[2.4,3)}}. Once
we compile against an updated jackrabbit-api we'll get a narrow import range of
{{org.apache.jackrabbit.api;version="[2.4,2.5)}}, which means that minor
version bumps of the exported version will make the bundle stop resolving.
> JcrBase: ProxyRepository implements JackrabbitRepository
> --------------------------------------------------------
>
> Key: SLING-12657
> URL: https://issues.apache.org/jira/browse/SLING-12657
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Reporter: Julian Reschke
> Priority: Major
>
> ...but that interface is of type "provider".
> See [https://cqdump.joerghoh.de/tag/providertype/] and
> [https://github.com/apache/jackrabbit-oak/blob/1939b6c15a1db13222c52e677ea48fdd7424bfb3/oak-jackrabbit-api/src/main/java/org/apache/jackrabbit/api/JackrabbitRepository.java#L28.]
> Any update to JackrabbitRepository (IMHO) will cause strange runtime
> behaviour.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
