[
https://issues.apache.org/jira/browse/JCRSITE-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742304#action_12742304
]
Jukka Zitting commented on JCRSITE-19:
--------------------------------------
Hmm, I hadn't considered that part of the license addendum. We already inline
the JCR API interfaces in the jackrabbit-standalone jar based on my earlier
interpretation of the "as part of a larger work", but that interpretation might
be a bit flawed. I'll check with Day management on whether this is a problem.
> Create OSGi wrapper for JCR API 1.0 library
> -------------------------------------------
>
> Key: JCRSITE-19
> URL: https://issues.apache.org/jira/browse/JCRSITE-19
> Project: Jackrabbit Site
> Issue Type: New Feature
> Components: wrapper
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: jcr api wrapper 1.0.0.000
>
> 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.
