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 6857] - jar manifest copies mf files wrong
Date Wed, 20 Mar 2002 13:25:19 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=6857>.
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=6857

jar manifest copies mf files wrong

conor@cortexebusiness.com.au changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From conor@cortexebusiness.com.au  2002-03-20 13:25 -------
OK, I have just committed an update to the Manifest code to maintain the order
or sections of attributes. Strictly speaking, according to the spec, this is not
required, but it makes for nicer looking manifests.

The truncation is actually a requirement of the spec. Lines longer than 72 must
be wrapped onto a "continuation" line, which starts with a space. Anything which
manipulates jars, and hence implements the jar spec should handle that. Can you
check if this is really an issue with your toolkit.

I am considering a nowrap flag since this causes so many issues and so many
systems don't implement the spec correctly. Let me know.

Please try the next nightly build.

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


Mime
View raw message