lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gunnar Wagenknecht (JIRA)" <j...@apache.org>
Subject [jira] Updated: (LUCENE-1344) Make the Lucene jar an OSGi bundle
Date Fri, 19 Sep 2008 08:30:44 GMT

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

Gunnar Wagenknecht updated LUCENE-1344:
---------------------------------------

    Attachment: LUCENE-1344.patch

Michael, the attached patch adds the bundle license header for the source bundles. I also
started to add descriptors for two more contrib jars (queries and xml parser). It gets a bit
messy now because of split-packages, i.e. the queries jar exports the same package (org.apache.lucene.search)
as Lucene core. This requires to add split packages headers to the manifests. Additional,
the "-" (dash) is invalid so I had to override the default bundle symbolic name for the xml-query-parser
jar. I use the package name.

The OSGi JARs don't need to be uploaded somewhere. It's enough to just put them on the FTP
mirrors next to the regular distribution.

Nicholas, we generate different JARs for OSGi because I don't like to mix and match things.
OSGi should be separated from Maven. They are different. For example, in OSGi it's a good
practice to name the JAR like the bundle symbolic name and to include the version. Otherwise
you'll run into problems because bundle repositories are usually not hierarchically organized
like Maven repos.

Michael, do we need a "-final" or "-dev" indicator on the JAR names and bundle versions?



> 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,
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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message