http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2295
*** shadow/2295 Tue Jul 10 10:42:15 2001 --- shadow/2295.tmp.8859 Wed Jul 18 07:25:04 2001 *************** *** 7,13 **** | Severity: Major OS/Version: HP-UX | | Priority: Other Component: Core tasks | +----------------------------------------------------------------------------+ ! | Assigned To: [EMAIL PROTECTED] | | Reported By: [EMAIL PROTECTED] | | CC list: Cc: | +----------------------------------------------------------------------------+ --- 7,13 ---- | Severity: Major OS/Version: HP-UX | | Priority: Other Component: Core tasks | +----------------------------------------------------------------------------+ ! | Assigned To: [EMAIL PROTECTED] | | Reported By: [EMAIL PROTECTED] | | CC list: Cc: | +----------------------------------------------------------------------------+ *************** *** 66,69 **** the jar file it doesnot work because it cannot find classes that are on the Manifest file classpath but are not wrapped properly. But when I manually jar the file using Sun's jdk 1.3 it does properly wrap the Manifest classpath, and ! my application runs fine from the jar file... --- 66,75 ---- the jar file it doesnot work because it cannot find classes that are on the Manifest file classpath but are not wrapped properly. But when I manually jar the file using Sun's jdk 1.3 it does properly wrap the Manifest classpath, and ! my application runs fine from the jar file... ! ! ------- Additional Comments From [EMAIL PROTECTED] 2001-07-18 07:25 ------- ! OK, I had a look at the JDK source and it will fail on lines longer than 512. ! The simplest would be to manipulate the manifests using the Manifest class ! through reflection (tedium). This would mean that jars generated by JDK 1.1 ! would not have correct manifests.
