You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2013/10/15 23:17:43 UTC

[jira] [Created] (SLING-3178) org.apache.sling.jcr.registration embeds ancient JCR-RMI classes

Jukka Zitting created SLING-3178:
------------------------------------

             Summary: org.apache.sling.jcr.registration embeds ancient JCR-RMI classes
                 Key: SLING-3178
                 URL: https://issues.apache.org/jira/browse/SLING-3178
             Project: Sling
          Issue Type: Bug
          Components: JCR
            Reporter: Jukka Zitting
            Priority: Minor


The mentioned component uses JCR-RMI version 2.0.0. This wouldn't be a problem if it only imported the exported API from that version, but it actually embeds parts of the JRC-RMI library, which makes it impossible to upgrade the RMI functionality without also changing this component.

A better approach would be to use normal imports for the relevant classes/packages.



--
This message was sent by Atlassian JIRA
(v6.1#6144)