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 11121] - manifest task does not follow Jar spec.
Date Fri, 26 Jul 2002 15:31:11 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=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.





------- Additional Comments From j_a_fernandez@yahoo.com  2002-07-26 15:31 -------
I have to say that this issue of the 72 chars has been around for quite some 
time. We have kept the hardline of (we do what the spec says and if you do not 
like it, use someting else). I wonder if we should reconsider our stand on 
this.

It is not only certain appServers, it is also any library that creates its own 
ClassLoaders and missed this particular issue. Notice that the bae classes in 
Java do nothing on your behalf, so there is really quite of room outthere to 
hit this problem. Is it too much to ask to have an attribute:

  useOutofSpecClasspathLongerThan72chars=true

Notice that the Class-Path thing did not show until 1.2, with no real support 
from the JVM itself.

--
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