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 23339] - Core Task War, Ear, Jar should have the M feature available
Date Tue, 23 Sep 2003 00:39:46 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=23339>.
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=23339

Core Task War, Ear, Jar should have the M feature available

conor@cortexebusiness.com.au changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From conor@cortexebusiness.com.au  2003-09-23 00:39 -------
If you don't want to create a manifest, use the <zip> task.

Your statement "Because of this, if the Class-Path value is longer than 71
characters a hard line is used and the filenames are broken up.  This makes the
Class-Path entry invalid for any listings after the end of the first line
(including a separated file on the first line)" is incorrect. Class-Path entries
greater than 72 chars are not valid according to the jar specification and must
be broken up into separate lines, using continuations (lines starting with a
space). Such an entry is not only not invalid, it is required. 

If Class-Path entries with continuations cause some systems to have problems,
then unfortunately, the problems lie with those systems and should be reported
to their developers.

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


Mime
View raw message