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

Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2010/01/19 15:17:54 UTC

[jira] Commented: (JCR-2470) Upgrade to jackrabbit-jcr-rmi 2.0

    [ https://issues.apache.org/jira/browse/JCR-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802271#action_12802271 ] 

Jukka Zitting commented on JCR-2470:
------------------------------------

As mentioned on dev@, I'm actually thinking of solving this by bringing jackrabbit-jcr-rmi and jackrabbit-jcr-servlet back to the main Jackrabbit trunk.

> Upgrade to jackrabbit-jcr-rmi 2.0
> ---------------------------------
>
>                 Key: JCR-2470
>                 URL: https://issues.apache.org/jira/browse/JCR-2470
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-standalone, jackrabbit-webapp
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>            Priority: Blocker
>             Fix For: 2.0.0
>
>
> Jackrabbit 2.0 should include the 2.0 version of the RMI component.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.