ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 6857] - jar manifest copies mf files wrong
Date Thu, 21 Mar 2002 08:29:17 GMT
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=6857>.
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=6857

jar manifest copies mf files wrong





------- Additional Comments From j_a_fernandez@yahoo.com  2002-03-21 08:29 -------
Can we make sure that our own code actually understand the jars as you are 
constructing them? Does this works with AntClassLoader? How about 
URLClassLoader?

I also think it is important to have a way to request that at least the 
classpath be left alone as a long line. There is too much code outthere that t 
does not follow this obscure spec. Can anyone give me a good reason why there 
is this need for 72 char lines in manifests? Is someone concerned about overrun 
buffers in java? (just a retorical question).

How about a "strict='true'" attribute that when true follows the 72 char split
and lives lines alone when false.

I know this is changing the subject a little, but it would be fantastic if we 
could add a <classpathset> fileset element that constructs the Class-Path line
from a list of jars. I could provide a patch if people think it would be a good 
idea.

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message