lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] Updated: (LUCENE-908) MANIFEST.MF cleanup (main jar and luci customizations)
Date Wed, 06 Jun 2007 00:40:26 GMT


Hoss Man updated LUCENE-908:

    Attachment: LUCENE-908.patch

quick pass at adopting some of the stuff i learned doing the Solr MANIFEST.MF ... i haven't
tested it extensively (Michael i'm hoping you can take the ball and run with it, i've got
about a million other things going on at the moment)

note: it was a while ago when i looked into all of this MANIFEST stuff and i'm not sure i
fully understood it then, let alone now.

patch moves jaring into a new macro (jarify) ... contribs can override the "jar-core" target
to call jarify and override some options as well as add new <attributes> to appear in
the manifest file.

manifest now includes a lot more information then it did before.

things this doesn't address...
  * manifest file in demo war file
  * manifest file in any of gdata's jars/war (it doesn't use the contrib-build.xml either)
  * spec version must match "digit+{.digit+}*" ... this is true for our official releases,
but broken in our nightlies.
  * need to svn remove the existing luci MANIFEST file
  * should luci's "Class-Path" refer to the full name of the lucene core jar?

> MANIFEST.MF cleanup (main jar and luci customizations)
> ------------------------------------------------------
>                 Key: LUCENE-908
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Build
>            Reporter: Michael Busch
>            Assignee: Michael Busch
>            Priority: Trivial
>             Fix For: 2.2
>         Attachments: LUCENE-908.patch
> there are several problems with the MANIFEST.MF file used in the core jar, and some inconsistencies
in th luci jar:
> Lucli's build.xml has an own "jar" target and does not use the jar target from common-build.xml.
The result
> is that the MANIFEST.MF file is not consistent and the META-INF dir does not contain
> Is there a reason why lucli behaves different in this regard? If not I think we should
fix this.

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