ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 21542] - Updated MANIFEST.MF doesn't get updated in JAR
Date Wed, 16 Jul 2003 07:49:01 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21542>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21542

Updated MANIFEST.MF doesn't get updated in JAR





------- Additional Comments From karsten.silz@epost.de  2003-07-16 07:49 -------
Here's what's in the ZIP:

Build files
base-build.xml, project-properties.txt, targets.txt, properties.txt

Listings after first build
log_jar_1.xml, ls_jar_1.txt, ls_manifest_1.txt

Listings after second build
log_jar_2.xml, ls_jar_2.txt, ls_manifest_2.txt


The target JARing things up is <integrate> in base-build.xml (line 283).  After
the first run, the MANIFEST.MF has a date of 20:30:59 (ls_manifest_1.txt) and
the JAR is fine (ls_jar_1.txt).  The build log is log_jar_1.xml (sorry, didn't
include the XSL); <integrate> starts there at line 59.  The XML listener is a
slightly modified version of the Ant one.

A couple of minutes later, I did another <integrate>.  The MANIFEST.MF got
updated and now has a date of 20:48:24 (ls_manifest_1.txt).  Now the build
recognized that the manifest got updated (log_jar_2.xml, line 49) - it did print
something like "Updating JAR because manifest was updated", which is not in the
log (why?).  It also omitted all files in there because they didn't change
(true) but did say nothing about the MANIFEST.MF.  But the JAR didn't change at
all (ls_jar_2.txt).

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message