Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <1916700478.1250069534801.JavaMail.jira@brutus>
Date: Wed, 12 Aug 2009 02:32:14 -0700 (PDT)
From: "Felix Meschberger (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Commented: (JCRSITE-19) Create OSGi wrapper for JCR API 1.0
 library
In-Reply-To: <1713056113.1249982970235.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Felix Meschberger commented on JCRSITE-19:
------------------------------------------

This would require a new version number or a new artifact id ;-)

But yes, this would be an option.

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