Bug 3413 - JCK 1.4 - BINC - detection of an IncompatibleClassChangeError (1GK7VCA)
Summary: JCK 1.4 - BINC - detection of an IncompatibleClassChangeError (1GK7VCA)
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: All Windows 2000
: P1 normal (vote)
Target Milestone: 2.0 M2   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 22:54 EDT by Olivier Thomann CLA
Modified: 2002-01-21 14:17 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Olivier Thomann CLA 2001-10-10 22:54:43 EDT
http://www.ott.oti.com/uvm/OTIIBM/numbat/Testing/JCK-
14/tests/lang/BINC/binc055/binc05501/binc05501.html - POSITIVE TEST
	This is a binary compatibility test. You need to compile the test cases 
in the same order I put them below one by one. And then execute it. The problem 
with the Eclipse
	compiler occurs only at runtime.

Test cases:

	javac 1.4:
		compilation: OK
		runtime: passed with java.lang.IncompatibleClassChangeError

	javac 1.3:
		compilation: OK
		runtime: failed

	Eclipse compiler:
		compilation: OK
		runtime: failed

NOTES:

	OT (19/09/2001 10:48:26 AM)
		In this case javac changes the declaring class of a field. The 
getfield bytecode is different.
	We can see that javac refers to binc05501c.i and we refer to 
binc05501s.i. Then we the declarations of binc05501s and binc05501i are changed 
we don't detect it,
	but javac does. The lookup for the field i leads to two fields (one for 
the interface and one for the super class). That would explain why an 
IncompatibleClassChangeError
	is thrown.
Comment 1 Philipe Mulet CLA 2002-01-21 14:17:13 EST
Adapted to this change for 1.4 mode only.
Fixed