You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2013/10/20 15:11:42 UTC

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

     [ https://issues.apache.org/jira/browse/SLING-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-3178.
-------------------------------------

    Resolution: Fixed

Thanks for your patch, it's applied in rev 1533884

> 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
>            Assignee: Carsten Ziegeler
>            Priority: Minor
>             Fix For: JCR Registration 1.0.0
>
>         Attachments: 0001-SLING-3178-org.apache.sling.jcr.registration-embeds-.patch
>
>
> 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)