[
https://issues.apache.org/jira/browse/LUCENE-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041321#comment-13041321
]
Daniele commented on LUCENE-1344:
---------------------------------
oh, well, the maven plugin just automatically generates the Manifest.mf
information bases on the actual code base. It works nice but is not the only
solution.
You can run http://bndtools.org/ against the jar to make a new jar with correct
Manifest OSGi instructions, that's what I did to make the 3.1.0 release work on
an OSGi environment. I think you can also integrate bnd with an ant script.
Or you can just keep the source Manifest file up to date, but you have to keep
exported packages (and version) aligned manually.
In the end is just a matter of releasing a jar with a few more meta information
in the standard Manifest.MF file, nothing more.
> 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
> Priority: Minor
> Attachments: LUCENE-1344-3.0-branch.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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
