jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Created: (JCRRMI-9) jackrabbit-api dependency is not optional
Date Wed, 01 Apr 2009 14:35:13 GMT
jackrabbit-api dependency is not optional
-----------------------------------------

                 Key: JCRRMI-9
                 URL: https://issues.apache.org/jira/browse/JCRRMI-9
             Project: Jackrabbit JCR-RMI
          Issue Type: Bug
            Reporter: Jukka Zitting
            Assignee: Jukka Zitting
             Fix For: 2.0


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.

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


Mime
View raw message