[
https://issues.apache.org/jira/browse/LUCENE-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley resolved LUCENE-1344.
-----------------------------------
Resolution: Fixed
Fix Version/s: 4.0
3.3
Lucene Fields: (was: [Patch Available, New])
merged with 3.x in r1130173
However this still does not have OSGi support in the official build.
For that, it seems like the right approach would be with bndtools. I will
resolve this issue, and we can make a new issue if someone wants to bite off
integrating with the ant build. The one thing i am against is somethign that
needs manual maintance everytime something changes.
> 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: general/build
> Reporter: Nicolas Lalevée
> Assignee: Ryan McKinley
> Priority: Minor
> Fix For: 3.3, 4.0
>
> Attachments: LUCENE-1344-3.0-branch.patch, LUCENE-1344-maven.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, lucene_trunk.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
