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 31833] - jar task mangles Name: entries in MANIFEST.MF for signed classes
Date Fri, 22 Oct 2004 16:06:04 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31833>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31833

jar task mangles Name: entries in MANIFEST.MF for signed classes





------- Additional Comments From conor@cortexebusiness.com.au  2004-10-22 16:06 -------
Just for future reference, please don't attach someone else's jars to a bug report. 

It would seem that changing the structure of the Name: line does indeed
invalidate the signature. I'm not sure why that is. 

There is a slight bug in Ant whereby the line limit check is not quite correct.
I will fix this presently. The effect of this is that Ant 1.6+ will create
Manifest lines up to 72 characters long - the limit should be 70 (allowing 2 for
the CR/LF)

I'll investigate further.

BTW, there is a slight issue in your copying of the manifest when building the
zip version since it won't overwrite the version extracted from the last jar -
you need to add an overwrite attribute there, I'd say.

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


Mime
View raw message