Hi, In order to have working JCR-RMI support included in Jackrabbit 2.0 we need to make a separate 2.0.0 release of the jackrabbit-jcr-rmi component. Last week I made a number of commits that made JCR-RMI usable with JCR 2.0. The layer doesn't pass the JCR 2.0 TCK and implements hardly any of the new JCR 2.0 interfaces, but all existing JCR 1.0 clients using JCR-RMI should still work with the new version.
The biggest issue I see with the release is that JCR-RMI currently depends on 2.0-beta versions of the jackrabbit-api and jackrabbit-jcr-commons components. I'm a bit reluctant to introduce a dependency in Jackrabbit 2.0.0 that refers to earlier 2.0-beta versions, though I'm not sure whether this has any negative impact in practice. I'll see what we can do about that. Unless any other major issues come up, I plan to cut the release candidate sometime next week. BR, Jukka Zitting
