You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Nicolas Lalevée (JIRA)" <ji...@apache.org> on 2008/07/23 20:17:33 UTC

[jira] Updated: (LUCENE-1344) Make the Lucene jar an OSGi bundle

     [ https://issues.apache.org/jira/browse/LUCENE-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nicolas Lalevée updated LUCENE-1344:
------------------------------------

    Attachment: LUCENE-1344-r679133.patch

Here is a patch against trunk.

The patch on common-build.xml allows the core or every contrib to package the jar as an OSGi bundle. When building, it just need a property "bundle.manifest.file" which is pointing to the template MANIFEST.MF to use. The patch on build.xml with the MANIFEST.MF makes lucene core jar an OSGi bundle.

Also in order to not have to maintain a third version scheme, I have added a /release target to compute the versions. So this doc should be updated :
http://wiki.apache.org/lucene-java/ReleaseTodo
{code}ant -Dversion=2.3.0-rc1 -Dspec.version=2.3.0 clean dist dist-src generate-maven-artifacts{code}
should be replaced by:
{code}ant /release clean dist dist-src generate-maven-artifacts{code}

Then about maintenance, the version in the MANIFEST.MF file is just usefull for people having the Lucene source in Eclipse and usin it as an OSGi bundle. The version is actually overridden while building the jar. And every new java package that is part of the Lucene API have to be added to the Export-Package header.



> 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: Build
>            Reporter: Nicolas Lalevée
>         Attachments: LUCENE-1344-r679133.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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org