http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2295
*** shadow/2295 Tue Jul 10 08:47:14 2001 --- shadow/2295.tmp.26485 Tue Jul 10 10:34:47 2001 *************** *** 49,52 **** ------- Additional Comments From [EMAIL PROTECTED] 2001-07-10 08:47 ------- Yes it causes functionality problems, because if the classpath line does not wrap properly, then it only uses the first line and does not pick up the rest of ! the stuff on the classpath and the program will not run properly...kyle --- 49,61 ---- ------- Additional Comments From [EMAIL PROTECTED] 2001-07-10 08:47 ------- Yes it causes functionality problems, because if the classpath line does not wrap properly, then it only uses the first line and does not pick up the rest of ! the stuff on the classpath and the program will not run properly...kyle ! ! ------- Additional Comments From [EMAIL PROTECTED] 2001-07-10 10:34 ------- ! Not sure what the last comment meant--if the line is not wrapped, surely it ! cannot be wrapped "improperly"--but anyway: the manifest specification says that ! lines must be wrapped at some number of characters, 70 or 72 I guess. And ! java.util.jar.Manifest does in fact perform this wrapping, and the JDK's jar ! tool uses it. That said, I do not know of any software which actually fails to ! correctly parse manifest lines of arbitrary length. Certainly Manifest class ! parses them fine even if they are long.
