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 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2003-09-08 00:57 ------- The tutorial is not the only mention of multiple Class-Path entries. Check out the extension spec http://java.sun.com/j2se/1.4.2/docs/guide/extensions/spec.html#bundled It contains this text "Multiple Class-Path headers may be specified, and are combined sequentially." While I would prefer to stick strictly to the jar spec, I do not believe Sun has been consistent enough to do so. It may even be due to some systems failing to process continuation lines correctly - don't know. I don't think the jar command line tool has historically done very much manifest checking, which probably has not helped. Given the current situation, I think support for multiple Class-Path headers is required. There are a few options though - a warning about multiple entries and possibly producing a single output Class-Path could be done. Please refer to this bug report for more info http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4683 I'll mark as WONTFIX for now, but please feel free to reopen and discuss --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
