[ 
https://issues.apache.org/jira/browse/JCR-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jukka Zitting updated JCR-3142:
-------------------------------

    Attachment: clirr-jackrabbit-webdav-2.3.0.txt
                clirr-jackrabbit-webdav-2.2.0.txt
                clirr-jackrabbit-webdav-2.1.0.txt

Attached clirr reports for changes in jackrabbit-webdav versions 2.1.0, 2.2.0 
and 2.3.0 when compared to the previous 2.x.0 version.

There are a few incompatible changes in each release, but nothing too major and 
nothing that we couldn't avoid if we paid closer attention (i.e. automatic test 
case) to API compatibility going forward.

And yes, as Felix notes, we always do have the option of upgrading the major 
package version when making incompatible API changes, so it's not too much of a 
problem. We'd just need to be more explicit about it than we've been so far.

To summarize, OK for exporting the o.a.j.webdav packages if (as it seems) we 
have consensus that the extra attention to compatibility is a good idea.
                
> 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, clirr-jackrabbit-webdav-2.1.0.txt, 
> clirr-jackrabbit-webdav-2.2.0.txt, clirr-jackrabbit-webdav-2.3.0.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

        

Reply via email to