DO NOT REPLY [Bug 30601] - Error in jar task
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=30601. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=30601 Error in jar task [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 30601] - Error in jar task
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=30601. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=30601 Error in jar task --- Additional Comments From [EMAIL PROTECTED] 2004-08-25 18:42 --- I'm having a similiar problem where the Class-Path line within MANIFEST.MF is being wrapped by the Jar task onto multiple lines at a 70 character line break. My goal has been to include a series of jars within my jar for easy distribution. after unpacking my jar I see : Manifest-Version: 1.0 Ant-Version: Apache Ant 1.6.2 Created-By: 1.4.2_04-b05 (Sun Microsystems Inc.) Main-Class: com.xoom.config.XoomEnv Class-Path: activation-1.0.2.jar commons-httpclient-2.0.jar commons-ne t-1.2.2.jar jython-2.1.jar lucene-1.4-rc3.jar mysql-connector-java-3. 0.14-production-bin.jar BlowfishJ.jar commons-logging.jar jline.jar . /log4j-1.2.8.jar mail-1.3.1.jar xmlrpc-1.2-b1.jar * but before packing the jar.. the MANIFEST.MF reads: Manifest-Version: 1.0 Ant-Version: Apache Ant 1.6.2 Created-By: 1.4.2_04-b05 (Sun Microsystems Inc.) Main-Class: com.xoom.config.XoomEnv Class-Path: activation-1.0.2.jar commons-httpclient-2.0.jar commons-net-1.2.2.jar jython-2.1.jar lucene-1.4-rc3.jar mysql-connector-java-3.0.14-production-bin.jar BlowfishJ.jar commons-logging.jar jline.jar ./log4j-1.2.8.jar mail-1.3.1.jar xmlrpc-1.2-b1.jar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 30601] - Error in jar task
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=30601. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=30601 Error in jar task --- Additional Comments From [EMAIL PROTECTED] 2004-08-25 18:50 --- This is normal, and as defined by the spec. The JDK jar command does the same thing. The Manifest as you type it or as a file outside a jar is different than the Manifest inside the JAR file, the latter following the Jar spec. --DD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 30601] - Error in jar task
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=30601. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=30601 Error in jar task --- Additional Comments From [EMAIL PROTECTED] 2004-08-25 21:37 --- It's clear that the MANIFEST spec says that lines cannot be longer than 72 chars. ( I won't try to speculate on the reason ). However, the problem lies in Manifest.java where the code which arbirarily wraps lines to no more than 70 characters does not attempt to wrap on white space. Instead it'll just chop a word into two pieces. This is roughly line 300 in the method writeValue. I would recommend changing this so that in addition to chopping it to no more than 70 chars, it will only do so on white space. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 30601] - Error in jar task
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=30601. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=30601 Error in jar task --- Additional Comments From [EMAIL PROTECTED] 2004-08-25 21:44 --- No need for that. The spec also says that continuation lines begin with a single space, and are merged with the space removed, so all the lines end up put together just fine. There are no known issues with the manifest format, and I and others use it with very long classpaths. So far all people claiming there was a bug there have been mistaken, and the problem lied either with faulty app servers not correctly reading JAR manifest, or an issue with the classpath itself (as opposed to the way it's formatted inside the JAR). --DD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 30601] - Error in jar task
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=30601. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=30601 Error in jar task --- Additional Comments From [EMAIL PROTECTED] 2004-08-12 14:54 --- Can you attach an example of such a jar (or the manifest file)? I'm not sure what these extra lines are and it is not clear to me how they could cause any problems in any case. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
