lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Parkes (JIRA)" <>
Subject [jira] Commented: (LUCENE-908) Lucli doesn't include standard MANIFEST.MF
Date Tue, 05 Jun 2007 21:43:26 GMT


Steven Parkes commented on LUCENE-908:

I'm pretty sure it's to get the stuff that's in the MANIFEST.MF in there: the Main-Class header,
in particular. With this, you can say java -jar jar w/o having to specify the main class.

Probably simplest just to also add the necessary files/lines manually? It's not DRY with the
code common-build.xml, but it's simple for an uncommon case.

> Lucli doesn't include standard MANIFEST.MF
> ------------------------------------------
>                 Key: LUCENE-908
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Build
>            Reporter: Michael Busch
>            Assignee: Michael Busch
>            Priority: Trivial
>             Fix For: 2.2
> Is there a particular reason why lucli has it's own MANIFEST.MF file? 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 does not contain infos like "Created-By Apache Lucene Java",
> neither does META-INF contain LICENSE.TXT and NOTICE.TXT.
> 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