lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gunnar Wagenknecht (JIRA)" <>
Subject [jira] Commented: (LUCENE-1344) Make the Lucene jar an OSGi bundle
Date Tue, 16 Sep 2008 13:24:44 GMT


Gunnar Wagenknecht commented on LUCENE-1344:

But it seems wrong to bind the versions order to the builds order. 

Not all the versions ... just those which appear to be of the *same* version (i.e., same tag
or branch). If it's a different version, you would change the numbers before the qualifier.
The qualifier really is just a build identifier. Giving it a meaning full name like {{{.rc1}}}
is a nice thing to have. But in relative this is hard to manage with automatic provisioning/update
systems. They usually handle automatic updates to a higher build of the same version or a
different build of a higher version fine.

> 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