lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée (JIRA) <>
Subject [jira] Commented: (LUCENE-1344) Make the Lucene jar an OSGi bundle
Date Wed, 10 Sep 2008 20:37:44 GMT


Nicolas Lalevée commented on LUCENE-1344:

About the missing header in the maven jar, this is weird because they exist in every other
jar in the distrib but in the maven one. And this is a lot more strange to see that the manifest
of the lucene core jar is in fact the manifest of the demo one... And I retested without the
patch, everything works correctly. I don't see yet how it can happen.

And the META-INF/MANIFEST.MF file doesn't have to be updated when releasing. The build process
is overriding the header entries. The file is mainly a template. See the {{build-bundle-manifest}}
macro in the patch.
But it will have to be updated after the release, just like the common-build.xml, to update
the version number.

> Make the Lucene jar an OSGi bundle
> ----------------------------------
>                 Key: LUCENE-1344
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Build
>            Reporter: Nicolas Lalevée
>            Assignee: Michael McCandless
>             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