[
https://issues.apache.org/jira/browse/JCR-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741861#action_12741861
]
Jukka Zitting commented on JCR-2254:
------------------------------------
Three more things:
* It would be good to include the JCR API version number right in the artifact
id, like this: "jcr-1.0-api". We're never going to release a bundle for JCR 2.0
(as it's already an OSGi bundle), and having the version number in the artifact
id makes it clearer that the real version number refers to our bundling and any
updates (we may need to release a patched version if there's some problem) will
not affect the bundled JCR 1.0 interfaces.
* It would be better to move this issue to the JCRSITE project that's best
suited for issues that don't clearly fit in any of the other Jira projects. I'd
like to keep this JCR project focused on the development of the Jackrabbit
repository implementation (including everything in jackrabbit/trunk).
* For the record, see LEGAL-50 for the issue where I'm asking ASF legal to
formally clear the Day spec license plus addendum as an OK license for
distribution by an Apache project. This is mostly just to complete the legal
record and is not a blocker for releasing this JCR API bundle. We have plenty
of precedent in redistributing the JCR API both as-is and in repackaged form.
> Create OSGi wrapper for JCR API 1.0 library
> -------------------------------------------
>
> Key: JCR-2254
> URL: https://issues.apache.org/jira/browse/JCR-2254
> Project: Jackrabbit Content Repository
> Issue Type: New Feature
> Components: JCR API
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Attachments: jcr-api-project.tgz
>
>
> To use the JCR API in OSGi frameworks it would make perfect sense to have
> separate OSGi bundles providing the API. For JCR 2.0 the library will come as
> an OSGi bundle. For JCR 1.0 the library is not an OSGi bundle and needs to be
> wrapped.
> For this, Jackrabbit should provide a simple wrapper bundle around the JCR
> library and export the respective API.
> This wrapper project would be part of the jackrabbit/commons proper and
> mainly be a service of Jackrabbit to the OSGi users out there.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
