[
https://issues.apache.org/jira/browse/JCR-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147759#comment-13147759
]
Jukka Zitting commented on JCR-3142:
------------------------------------
I'd go with BND annotations, as that's what we already use in jackrabbit-api
and jackrabbit-jcr-commons. There I started with package version 2.3 for those
packages that already were exported in previous versions and 1.0 for any new
packages. For jackrabbit-webdav I'd start the package versions at 1.0 to
emphasize that they're different from Jackrabbit release versions (they reflect
API changes separately for each package instead of globally for the whole
product).
> 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
