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] New: - manifest task does not follow Jar spec.
Date Wed, 24 Jul 2002 08:49:55 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.

           Summary: manifest task does not follow Jar spec.
           Product: Ant
           Version: 1.5
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Optional Tasks
        AssignedTo: ant-dev@jakarta.apache.org
        ReportedBy: kisst2@freemail.hu


The manifest task wraps lines longer than 72 characters, which also stated in 
the javadoc for this task:
"If an application can not handle the continuation mechanism, it is a defect in 
the application, not this task."

However, the Jar spec dictates, that manifest attributes like Class-Path should 
always be a single line. (even if it is longer than 72 chars.)

Currently, specifying a long Class-Path attribute breaks ClassLoaders.

Quick and dirty solution would be to set the MAX_LINE_LENGTH attribute to 
Integer.MAX in org.apache.tools.ant.taskdefs.Manifest.java.

Better one would be to rewrite the writeValue method, not to wrap.

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