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 07:29:44 GMT


Gunnar Wagenknecht commented on LUCENE-1344:

I would love to see bundle headers in the manifests. 

RE: {{{2.3.0 < 2.3.0.rc1}}} 
One way to handle this problem is byI using a timestamp as qualifier when generating the version
number. This ensures that each new build is of a higher version. At Eclipse we use a ".qualifier"
suffix which will be replaced with the actual CVS/SVN tag at build time. The CVS/SVN tag is
actually a timestamp "v20080916-1020" or just an increasing number (eg., "v1, v2, v3...").
It depends on what a project favors. I could also imaging that this would be the SVN revision
at build time.

> 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