lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Commented: (LUCENE-1344) Make the Lucene jar an OSGi bundle
Date Thu, 18 Sep 2008 16:22:44 GMT


Michael McCandless commented on LUCENE-1344:

OK I was able to generate the OSGI bundles. But, a few questions.

Under dist/osgi I see these files:

-rw-rw-rw-  1 mike  staff    5408 Sep 18 12:08 org.apache.lucene.core_2.4.0.200809181201.jar
-rw-rw-rw-  1 mike  staff  770986 Sep 18 12:08 org.apache.lucene.core.source_2.4.0.200809181201.jar
-rw-rw-rw-  1 mike  staff    5412 Sep 18 12:08 org.apache.lucene.analyzers_2.4.0.200809181208.jar
-rw-rw-rw-  1 mike  staff  431926 Sep 18 12:08 org.apache.lucene.analyzers.source_2.4.0.200809181208.jar
-rw-rw-rw-  1 mike  staff    5410 Sep 18 12:08 org.apache.lucene.memory_2.4.0.200809181208.jar
-rw-rw-rw-  1 mike  staff   37197 Sep 18 12:08 org.apache.lucene.memory.source_2.4.0.200809181208.jar
-rw-rw-rw-  1 mike  staff    5414 Sep 18 12:08 org.apache.lucene.highlighter_2.4.0.200809181208.jar
-rw-rw-rw-  1 mike  staff   45676 Sep 18 12:08 org.apache.lucene.highlighter.source_2.4.0.200809181208.jar

Shouldn't we make OSGI bundles for all contrib packages, and core & demo?

The source jar actually has .java sources, but the binary jars only have META-INF subdir,
eg org.apache.lucene.core_2.4.0.200809181201.jar unzips to:

Archive:  dist/osgi/org.apache.lucene.core_2.4.0.200809181201.jar
  inflating: META-INF/MANIFEST.MF    
  inflating: META-INF/LICENSE.txt    
  inflating: META-INF/NOTICE.txt     

Is that right?  Shouldn't this jar have the .class files?

At a higher level, can't we have the normal JARs produced by the build simply include the
necessary OSGI headers in the manifest?  (Why make new JARs?).

Finally, during the release process, what should we do with the OSGI bundles?  EG the Maven
artifacts are copied to a distribution directory so that they are pushed to the central Maven

> 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
>         Attachments: LUCENE-1344-r679133.patch, LUCENE-1344-r690675.patch, LUCENE-1344-r690691.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:
For additional commands, e-mail:

View raw message