lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Commented: (LUCENE-1344) Make the Lucene jar an OSGi bundle
Date Sun, 07 Sep 2008 11:03:44 GMT


Michael McCandless commented on LUCENE-1344:

Thanks Nicolas.  I understand a bit more now :)

One problem: even though I was able to successfully run the above command, the resulting MANIFEST.MF
in the Lucene core JAR (dist/maven/org/apache/lucene/lucene-core/2.3.0/lucene-core-2.3.0.jar)
does not have any of your added lines (eg Export-Package) -- do you see this too?

About the different version schemes, yep, this is yet another one to maintain. The version
number taken into account in a OSGI environment is "Bundle-Version", I don't know what the
header "Specification-Version" is used for. I tried to refactor a little bit in the build
system to generate the version numbers, but I failed, a more bigger patch would be needed
(I am willing to do some if needed).
I think it's OK for now if we have to update the versions in META-INF/MANIFEST.MF manually
as part of the release process?  (It sounds hard to get the build to autogen the versions).

> Make the Lucene jar an OSGi bundle
> ----------------------------------
>                 Key: LUCENE-1344
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Build
>            Reporter: Nicolas Lalevée
>             Fix For: 2.4
>         Attachments: LUCENE-1344-r679133.patch, LUCENE-1344-r690675.patch, LUCENE-1344-r690691.patch,
> 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:
For additional commands, e-mail:

View raw message