[
https://issues.apache.org/jira/browse/JCR-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741852#action_12741852
]
Jukka Zitting commented on JCR-2254:
------------------------------------
Looks good, +1 to committing this in jackrabbit/commons/jcr-api/trunk.
Some suggestions:
* Add README, LICENSE, and NOTICE files at the top level of the project. These
are for people checking the sources from svn or using a source release.
* Use src/main/appended-resources for the LICENSE and NOTICE customizations.
The remote resource plugin will pick them up from there and append append to
the vanilla Apache LICENSE and NOTICE files.
* The apache parent POM we're using already enables the GPG plugin, so there's
no need to define it again in the project POM.
* Same applies to the RAT plugin. It's already enabled by the Jackrabbit parent
POM version 3.
It's probably easier to apply these changes once the baseline code is in svn.
> 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.
