Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
The original idea for implementing the jackrabbit-api extensions in JCR-RMI was to only require the jackrabbit-api dependency when both the client and the server used those extensions. However, in practice the way we implemented the extensions requires the client (and rmiregistry, if used) of a Jackrabbit server to include the jackrabbit-api regardless of whether those extensions are used or not.
This is a bit unfortunate, but as there is no easy way to work around this issue, I'm going to make the jackrabbit-api dependency non-optional in JCR-RMI. This should help avoid some common classpath configuration errors.