Error opening zip file ant

Is the jar file valid? Can you open it in a WinZip or other compression tool? Cheers — Alastair Brayne. Why not move your comment to an answer and then accept it? This might prove to be a useful question for someone, but at the moment it shows as 'unanswered'.

AlastairBrayne Facing the exact same problem. Nothing worked till now. Add a comment. Active Oldest Votes. As per Martin Clayton's suggestions, my previous comment is copied below as an answer.

Improve this answer. I had loads of hidden jars.! Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. If you are creating jars, then java. We recommend you set the encoding to UTF-8 and keep the language encoding flag enabled. The flag won't help or hurt java. For maximum interoparability it is probably best to set the encoding to UTF-8, enable the language encoding flag and create Unicode extra fields when writing ZIPs.

Such archives should be extracted correctly by java. They will be unusable with Windows' "compressed folders" feature and bigger than archives without the Unicode extra fields, though. If Windows' "compressed folders" is your primary consumer, then your best option is to explicitly set the encoding to the target platform.

You may want to enable creation of Unicode extra fields so the tools that support them will extract the file names correctly. Zip64 extensions provide a way to create archives bigger than 4 GB or holding more than entries—or add individual entries bigger than 4 GB using the ZIP extension field mechanism.

These extensions are supported by most modern ZIP implementations. When Ant writes compressed entries into the archive it creates it doesn't know the compressed size of an entry before it has been written. Unfortunately the decision whether a Zip64 extra field will be written has to be made before writing the entry's content.

Ant 1. It supports three values: never means no Zip64 extra fields will ever be written. This is the behavior of Ant prior to 1. This is the default behavior of Ant 1. Unfortunately some ZIP implementations don't understand Zip64 extra fields or fail to parse archives with extra fields in local file headers that are not present in the central directory, one such implementation is the java.

Archives created with as-needed can be read without problems with Java 6 and later. Prior to Ant 1. Each file found in this fileset is added to the archive the same way that zipfileset src files are added. If manual. Files in the directory mydocs , or files with the name todo. Only html files under the directory api are zipped, and files with the name todo. Not only store data but also compress them. Unless you set the keepcompression attribute to false , this will apply to the entire archive, not only the files you've added while updating.

For entries coming from existing archives like nested zipfileset s or while updating the archive , keep the compression as it has been originally instead of using the compress attribute. The character encoding to use for filenames inside the zip file. For a list of possible values see the Supported Encodings. Valid values are fail , skip , and create.

Priority: Blocker. Resolution: Cannot Reproduce. Labels: configuration plugins. Environment: Hide 1. Installed Jenkins 2. Windows service is running 3.

Java JRE7 5. Windows R2 Standard I'm marking the bug as blocker since it is blocked my activity.