jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Klimetschek (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-1991) Create osgi bundles for all jars
Date Wed, 09 Sep 2009 11:09:57 GMT

     [ https://issues.apache.org/jira/browse/JCR-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alexander Klimetschek updated JCR-1991:
---------------------------------------

    Attachment: jcr1991-spi.patch

Nevertheless, here is a patch for bundleizing spi and spi-commons.

To be in line with jackrabbit-api, which is already a bundle, we might want to change the
project names to be "Apache Jackrabbit ..." instead of just "Jackrabbit ...".  This is handy
because OSGi frameworks often list bundles by their name. Apache Sling for example has the
"Apache" prefix for all their bundles. WDYT?

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


Mime
View raw message