Uploaded image for project: 'Jackrabbit JCR-RMI'
  1. Jackrabbit JCR-RMI
  2. JCRRMI-9

jackrabbit-api dependency is not optional

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.6.0
    • 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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            jukkaz Jukka Zitting
            jukkaz Jukka Zitting
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment