[
https://issues.apache.org/jira/browse/JCR-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755427#action_12755427
]
Michael Dürig commented on JCR-1991:
------------------------------------
I was looking into bundling jackrabbit-jcr2spi. But actually jackrabbit-jcr2spi
has nothing to export by itself. So I came to the conclusion that instead of
providing it as an bundle by itself, it might be better to make it part of a
bundle which exports a RepositoryFactory implementation. Here
jackrabbit-jcr-client comes to mind. However, jcr-client has a lot of
dependencies (inkl. several spi implementations). So what about removing these
dependencies from jcr-client by dynamically loading the required classes and
then making it into a bundle?
> Create osgi bundles for all jars
> --------------------------------
>
> Key: JCR-1991
> URL: https://issues.apache.org/jira/browse/JCR-1991
> Project: Jackrabbit Content Repository
> Issue Type: Sub-task
> Components: jackrabbit-core, jackrabbit-jca,
> jackrabbit-jcr-benchmark, jackrabbit-jcr-server, jackrabbit-jcr-tests,
> jackrabbit-jcr2spi, jackrabbit-spi, jackrabbit-spi-commons,
> jackrabbit-spi2jcr, jackrabbit-text-extractors, jackrabbit-webdav
> Reporter: Martin Zdila
> Attachments: jcr1991-spi.patch
>
>
> I think that also jackrabbit-text-extractors, jackrabbit-spi-commons,
> jackrabbit-spi and jackrabbit-core libraries should be budles. How could we
> otherwise use Jackrabbit in the OSGi environment if not all required
> libraries are bundles? You maybe could also provide jcr-1.0.jar as OSGi
> bundle. Current;y I must create bundles from forementioned libraries by using
> the bnd tool. Thanks in advance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
