lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-1344) Make the Lucene jar an OSGi bundle
Date Thu, 04 Sep 2008 14:51:56 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628348#action_12628348
] 

Michael McCandless commented on LUCENE-1344:
--------------------------------------------


Nicolas, does this mean we need to maintain the new
META-INF/MANIFEST.MF, manually?  Ie on each release go edit it & bump
up the versions in there?  (We need to update the wiki to this effect
too)

There are quite a few "copies" of version in there, and for example we
have Bundle-Version: 2.4.0.dev and then Specification-Version:
2.4.0-dev -- is that right?  (Ie, one uses "." and the other uses
"-").

I was able to generate a release candidate using your command above.
What command would be used to generate the actual release?  (Ie, what
to specify for version, spec.version and bundle.version?).

{quote}
So 2.3.0 < 2.3.0.rc1. But 2.3.0.alpha1 < 2.3.0.beta1 < 2.3.0.beta2 < 2.3.0.cr1
< 2.3.0.final
{quote}

OK I'm a little confused by this.  What does "cr1" mean?  And, while I
can see the lexicographic sort order, your first case (2.3.0 <
2.3.0rc1) seems backwards because 2.3.0rc1 ("release candidate 1")
arrives before 2.3.0 (this is the released 2.3.0 right?) in time,
whereas in the 2nd case those releases are in time order.  I'm
confused.

Sorry for the silly questions -- I know very little about OSGi bundles!

> 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
>             Fix For: 2.4
>
>         Attachments: LUCENE-1344-r679133.patch, LUCENE-1344-r690675.patch, LUCENE-1344-r690691.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