[
https://issues.apache.org/jira/browse/LUCENE-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirby Bohling updated LUCENE-1344:
----------------------------------
Attachment: LUCENE-1344-3.0-branch.patch
Attaching a patch that generates a sibling jar file (hopefully it will replace
the original Jar files before it is actually committed) that includes all of
the OSGi Manifest requirements.
All the regular unit tests appear to pass if I use the OSGi bundles instead of
the standard jar files (by removing the <jar> task in the <jarify> macro
defined in commons-build.xml, and modifying the <bnd> task to use
output="@{destfile}". The backward compat tests appear to fail, but I haven't
gotten to the bottom of that just yet.
It requires that the biz.aQute.bnd.jar be in the lib/ directory.
>From this site:
http://www.aqute.biz/Bnd/Download
I grabbed it off of this link:
http://dl.dropbox.com/u/2590603/bnd/biz.aQute.bnd.jar
The bnd jar is a standard tool for generating valid and up-to-date OSGi headers
with minimal problems.
I downloaded the commons-math jar file to see the set of headers the commons
projects added to their bundles.
I have not tested any of the contrib bundles in an OSGi environment, but I am
using the Lucene Core bundle generated by this. It is also likely that the
${Name} value should be set in all of the sub-directories to generate better
human consumable names for the bundles, currently they are all set to "Lucene".
Potentially a better description would be useful also. I believe a couple
will have problems (lucli being the most obvious because it isn't in the
org.apache.lucene package structure). I can do more testing and ensure as much
as I can works if this patch would be applied.
I can port and update this to the 4.0 branch if desirable, and it should be
simple to modify to just generate the final Jar files.
> Make the Lucene jar an OSGi bundle
> ----------------------------------
>
> Key: LUCENE-1344
> URL: https://issues.apache.org/jira/browse/LUCENE-1344
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Build
> Reporter: Nicolas Lalevée
> Priority: Minor
> Attachments: LUCENE-1344-3.0-branch.patch, LUCENE-1344-r679133.patch,
> LUCENE-1344-r690675.patch, LUCENE-1344-r690691.patch,
> LUCENE-1344-r696747.patch, LUCENE-1344.patch, LUCENE-1344.patch,
> LUCENE-1344.patch, LUCENE-1344.patch, LUCENE-1344.patch, LUCENE-1344.patch,
> MANIFEST.MF.diff
>
>
> In order to use Lucene in an OSGi environment, some additional headers are
> needed in the manifest of the jar. As Lucene has no dependency, it is pretty
> straight forward and it ill be easy to maintain I think.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
