[ 
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-r696747.patch

I have fixed my patch so the maven jar does contain the OSGi manifest, even if 
I don't understand really why the jar are generated twice.
This new patch contains improvements.
* as suggested by Gunnar, the bundle version will be 2.9.0.$TIMESTAMP-dev.
* the version of the export package in the header are now controlled by the ant 
task


So the command to build a rc version will be:
{noformat}ant -Dspec.version=2.4.0 -Dqualifier.version=rc1 clean dist dist-src 
generate-maven-artifacts{noformat}
will generate:
* a lucene-core-2.4.0-rc1.jar
* a lucene-core-2.4.0-rc1.zip
* a maven artifact in 
org/apache/lucene/lucene-core/2.4.0-rc1/lucene-core-2.4.0-rc1.jar
* the jars will contain the bundle version: 2.4.0.20080918220130-rc1


For a final version:
{noformat}ant -Dspec.version=2.4.0 -Dqualifier.version=final clean dist 
dist-src generate-maven-artifacts{noformat}
will generate:
* a lucene-core-2.4.0-final.jar
* a lucene-core-2.4.0-final.zip
* a maven artifact in 
org/apache/lucene/lucene-core/2.4.0-final/lucene-core-2.4.0-final.jar
* the jars will contain the bundle version: 2.4.0.20080918220130-final


I know that Lucene distrib used to not add qualifier to the final release, it 
can still be done with:
{noformat}ant -Dspec.version=2.4.0 -Dqualifier.version=final -Dversion=2.4.0 
clean dist dist-src generate-maven-artifacts{noformat}
will generate:
* a lucene-core-2.4.0.jar
* a lucene-core-2.4.0.zip
* a maven artifact in org/apache/lucene/lucene-core/2.4.0/lucene-core-2.4.0.jar
* the jars will contain the bundle version: 2.4.0.20080918220130-final



> 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
>            Assignee: Michael McCandless
>         Attachments: 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, 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.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to