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

Hoss Man updated LUCENE-908:
----------------------------

    Description: 
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 LICENSE.TXT and NOTICE.TXT.

Is there a reason why lucli behaves different in this regard? If not I think we 
should fix this.

  was:
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.

        Summary: MANIFEST.MF cleanup (main jar and luci customizations)  (was: 
Lucli doesn't include standard MANIFEST.MF)

> MANIFEST.MF cleanup (main jar and luci customizations)
> ------------------------------------------------------
>
>                 Key: LUCENE-908
>                 URL: https://issues.apache.org/jira/browse/LUCENE-908
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Build
>            Reporter: Michael Busch
>            Assignee: Michael Busch
>            Priority: Trivial
>             Fix For: 2.2
>
>
> 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 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to