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 14:11:45 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 ddevienne@lgc.com  2002-07-26 14:11 -------
Well, the jar spec still says that lines in the Manifest are limited to 72 
characters, so the Class-Path: entry shown should wrap on a second line, which 
must start with a space (indicating line continuation). Wrapping can happen in 
the middle of words, and things work fine.

The approach I use is to define the Manifest by hand with

Class-Path: %CLASSPATH%

And perform the substitution are at build time. After substitution, one jar 
appears per line:

Class-Path:
 ./lib/jar1
 ./lib/jar2

And after being precessed by Ant/jar.exe, it appears as,

Class-Path: ./lib/jar1 ./lib/jar2 ...

with proper wrapping in the middle of words if the Class-Path: line exceeds 72 
characters (continues on next line starting with a space).

The only problem I see is if one classpath entry exceeds 71 characters (before 
being processed by Ant/jar.exe), but this should rarely happen, since the path 
are relative to the jar that contains the manifest defining the Class-Path.

I hope this sheds a little light on the subject. --DD

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