You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (Jira)" <ji...@apache.org> on 2020/08/04 15:12:00 UTC
[jira] [Resolved] (SLING-9629) Jackrabbit RMI imports no longer
marked as optional
[ https://issues.apache.org/jira/browse/SLING-9629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Munteanu resolved SLING-9629.
------------------------------------
Resolution: Fixed
Fixed with [sling-org-apache-sling-jcr-base commit 985bb2a|https://github.com/apache/sling-org-apache-sling-jcr-base/commit/985bb2a].
> Jackrabbit RMI imports no longer marked as optional
> ---------------------------------------------------
>
> Key: SLING-9629
> URL: https://issues.apache.org/jira/browse/SLING-9629
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Critical
> Fix For: JCR Base 3.1.4
>
>
> After the fix for SLING-9627 the org.apache.jackrabbit.rmi.client, org.apache.jackrabbit.rmi.remote imports are no longer marked as optional. This means the bundle does not resolve on deployments where the RMI bundles are not present, which is unexpected and undesired.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)