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 17123] - Build Process failed on OS/390, Default Manifes is invalid
Date Mon, 17 Feb 2003 17:46:02 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=17123>.
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=17123

Build Process failed on OS/390, Default Manifes is invalid





------- Additional Comments From bnsbr@tecnolink.com.br  2003-02-17 17:46 -------
I think I solved the problem. I modified the Manifest task, the method 
getDefaultManifest(), there you use a InputStream in ASCII mode to copy the 
manifest file. I removed the "ASCII" param at the call for the constructor and 
it worked. Now the build process is Ok. But I got one error with the "ant" 
and "antRun" files at bootstrap/bin, I think they are created in ASCII and 
because of it they are invalid. I workout this sending to Mainframe the ant and 
antRun file generated at Windows. Sending they as text to Mainframe cause the 
conversion to EBCDIC. So, the only problem is the generated ant and antRun file.
Betwen, I have read at specification of ant that when you dont inform the place 
that ant dist should be installed the ant dist is generated in ANT_HOME dir, 
that is on enviroment variable. But this didn't work.

Mime
View raw message