jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-3142) Create OSGi Bundles from jackrabbit-webdav and jackrabbit-jcr-server libraries
Date Thu, 10 Nov 2011 13:59:52 GMT

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

angela commented on JCR-3142:

> I'm a bit concerned about exporting the entire jackrabbit-webdav API. So far we haven't
made strict backwards compatibility 
> promises beyond jackrabbit-api and jackrabbit-jcr-commons (where we now explicitly manage
the exported OSGi package versions), 
> and exporting all the o.a.j.webdav packages significantly increases our public API footprint.

we never made promises :) 
but being the author of the webdav-library: i treated it as public API since it became the
replacement of the retired slide project [1].
in fact i do remember a couple of api extensions, a major xml-related refactoring in the very
beginning  and quite some bug fixes. can
we easily find out how often we were breaking strict backwards compatibility?

[1] http://jakarta.apache.org/slide/
> Create OSGi Bundles from jackrabbit-webdav and jackrabbit-jcr-server libraries
> ------------------------------------------------------------------------------
>                 Key: JCR-3142
>                 URL: https://issues.apache.org/jira/browse/JCR-3142
>             Project: Jackrabbit Content Repository
>          Issue Type: New Feature
>          Components: jackrabbit-jcr-server, jackrabbit-webdav
>    Affects Versions: 2.3.2
>            Reporter: Felix Meschberger
>         Attachments: bundleize-davex.txt
> Propose to generate bundles from the jackrabbit-webdav (exporting everything) and jackrabbit-jcr-server
(exporting nothing) libraries. In addition a new class is added to the jackrabbit-jcr-server
library, which in case of deployment in an OSGi framework will register a Servlet with the
OSGi HttpService to expose the JcrRemotingServlet.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message