[
https://issues.apache.org/jira/browse/JCR-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741870#action_12741870
]
Felix Meschberger commented on JCR-2254:
----------------------------------------
> library version
Current the setup is similar to what we do in the Apache Felix wrappers: append
a wrapper build counter to the original wrapped library version. So the initial
release of this wrapper will be something like jcr-api-1.0.0.000. If ever we
would have to re-release the wrapper the build counter would be increased thus
giving something like jcr-api-1.0.0.002.
Of course the export version of the javax.jcr API packages is fixed at 1.0 and
will not change as long as we wrap the 1.0 version of the API.
> 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
> 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.
