-
Bug
-
Resolution: Fixed
-
P1
-
5.0
-
b42
-
x86
-
windows_98, windows_2000
Name: gm110360 Date: 02/09/2004
FULL PRODUCT VERSION :
java version "1.5.0-beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-beta-b32c)
Java HotSpot(TM) Client VM (build 1.5.0-beta-b32c, mixed mode)
ADDITIONAL OS VERSION INFORMATION :
Windows 98 [Version 4.10.1998]
A DESCRIPTION OF THE PROBLEM :
The application I created and ran fine with Java 1.4.2_01-b06 now returns Invalid or corrupt jarfile with 1.5Beta.
I tracked what the problem was and it seems to be the open source obfuscator Retroguard. Note that other software obfuscated with Retroguard works ok with 1.5Beta.
The particulary of my file was that it used
.attribute SourceFile to preserve the source file attribute
.attribute LineNumberTable to preserve the line number table
I submitted this bug hoping you would be interested to know and that using your bedug tools you could point to what went wrong. If not you can close this bug.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Download http://www.antcommander.com/AntCommander-pb.zip
unzip it and execute java -jar AntCommander.jar
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
A nice GUI ;-)
ACTUAL -
D:\Lg\AntCommander\0.7\test2>java -jar AntCommander.jar
Invalid or corrupt jarfile AntCommander.jar
ERROR MESSAGES/STACK TRACES THAT OCCUR :
Invalid or corrupt jarfile AntCommander.jar
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
Don't obfuscate or use java 1.4.2
Release Regression From : 1.4.2_03
The above release value was the last known release where this
bug was known to work. Since then there has been a regression.
(Incident Review ID: 237682)
======================================================================
- relates to
-
JDK-6196163 'Invalid or corrupt jarfile' due to 1.5 backport
- Closed