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=17075>. 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=17075 codepage problems with manifest file when using jar task Summary: codepage problems with manifest file when using jar task Product: Ant Version: 1.5.1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: Other Component: Core tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The OS is IBM z/OS 1.2. When using the jar task on z/OS, the manifest.mf cannot be read. (The error is also on ear and war tasks). When the manifest file is in ascii format (having been transmitted as binary from the IDE to the z/OS based source control system) The following error is produced: [jar] Manifest is invalid: Manifest line "(/>ัรมหศ๎มสหั?> BUILD FAILED file:/home/t129563/projects/deploy/genericUBSbuild.xml:32: Invalid Manifest: /home/t129563/projects/trade2v2/TradeEJBs/bin/META-INF/MANIFEST.MF at org.apache.tools.ant.taskdefs.Jar.getManifest(Jar.java:225) at org.apache.tools.ant.taskdefs.Jar.getManifest(Jar.java:201) at org.apache.tools.ant.taskdefs.Jar.createManifest(Jar.java:284) etc.... The manaifest class is using a Reader and therefore trying to translate from native encoding (IBM-1047). But the file is not in nmative encoding, and it would not be natural for it to be under these circumstances (in a source control repository). When the manfiest on z/OS is in EBCDIC format (for the purposes of testing this) , then the build runs through OK but the resulting manifest file in the jar is still in EBCDIC format and is therefore useless.
