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=22967>. 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=22967 <jar> permits duplicated manifest attributes in violation of the manifest specification ------- Additional Comments From [EMAIL PROTECTED] 2003-09-09 01:21 ------- I think we are OK here. For your point 1, this is mostly already the case. Only Class-Path headers may be duplicated in a section. All others will generate the original exception you saw in Ant 1.4.x. We don't currently warn about duplicate Class-Path headers but we can add that. Class-Path attributes are not merged but are retained as separate entities and output in that form. An option to coalesce into a single entry could be supported. Should it be mandatory? Probably not. For your point 2, this is not necessary. Ant will never generate a manifest which is longer than 72 bytes long, using continuation lines where necessary. The 512 byte limit in the JDK manifest parsing code relates to individual lines, not the total attribute value. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
