ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 2295] - Core Task Jar does not proplerly wrap classpath lines longer than 70 chars.
Date Tue, 10 Jul 2001 17:42:15 GMT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2295

*** shadow/2295	Tue Jul 10 10:34:47 2001
--- shadow/2295.tmp.26976	Tue Jul 10 10:42:15 2001
***************
*** 58,61 ****
  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.
--- 58,69 ----
  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.
! 
! ------- Additional Comments From kyle@zxmail.com  2001-07-10 10:42 -------
! Well when I use the ant jar process I get the results I posted earlier, where 
! the classpath doesn't wrap at 70-72, and when I try to run my application from 
! 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...

Mime
View raw message