[ 
https://issues.apache.org/jira/browse/JCRSITE-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742256#action_12742256
 ] 

Marcel Reutegger commented on JCRSITE-19:
-----------------------------------------

> We have plenty of precedent in redistributing the JCR API both as-is and in 
> repackaged form.

I don't see a problem with redistributing the JCR API jar file as-is, however 
the addendum does not seem to allow repackaging. It says:

"In addition to the permissions granted under the Specification
    License, Day Management AG hereby grants to You a perpetual,
    worldwide, non-exclusive, no-charge, royalty-free, irrevocable
    license to reproduce, publicly display, publicly perform,
    sublicense, and distribute unmodified copies of the Content
    Repository for Java Technology API (JCR 1.0) Java Archive (JAR)
    file ("jcr-1.0.jar") and to make, have made, use, offer to sell,
    sell, import, and otherwise transfer said file on its own or
    as part of a larger work that makes use of the JCR API."


The part that worries me in the context of this issue is:

"[...] unmodified copies of the Content Repository for Java Technology API (JCR 
1.0) Java Archive (JAR) file ("jcr-1.0.jar") [...]"

Is it possible to create a bundle that includes the jcr jar file as is?

> 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.

Reply via email to