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=11121>. 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=11121 manifest task does not follow Jar spec. [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2002-07-26 14:03 ------- Settings as invalid. Manifest mf = new Manifest(); Manifest.Attribute attr = new Manifest.Attribute("Class-Path" , "a.jar b.jar c.jar d.jar e.jar f.jar g.jar h.jar i.jar j.jar k.jar l.jar m.jar n.jar o.jar" ); mf.addConfiguredAttribute(attr); PrintWriter wri = new PrintWriter( new FileWriter("1.mf") ); mf.write( wri ); wri.close(); java.util.jar.Manifest mf2 = new java.util.jar.Manifest(new FileInputStream ("1.mf")); System.out.println("Class-Path: " + mf2.getMainAttributes().getValue("Class- Path") ); mf2.write( new FileOutputStream("2.mf") ); In both case (Ant and JDK) it writes: Class-Path: a.jar b.jar c.jar d.jar e.jar f.jar g.jar h.jar i.jar j.ja r k.jar l.jar m.jar n.jar o.jar And the Class-Path line is read perfectly so the error is not here but in your app server. If it can satisfy you, you're not alone as Weblogic will crash if there is a jar in the classpath entry that do not exist. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
