Bug 3417 - JCK 1.4 - BINC - the new method is a static (respectively instance) method. (1GK7WCP)
Summary: JCK 1.4 - BINC - the new method is a static (respectively instance) method. (...
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:19 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

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:46 EDT 
http://www.ott.oti.com/uvm/OTIIBM/numbat/Testing/JCK-
14/tests/lang/BINC/binc058/binc05802/binc05802.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 12:50:45 PM)
		Same explanation than 1GK7VXD: ITPJCORE:WIN2000 - JCK 1.4 - the 
new method is less accessible than the old one.
		The bytecode used is a getfield. But with the changes the 
method is static. Then javac refers to 
javasoft.sqe.tests.lang.binc058.binc05802.binc05802c and find the
		intermediate static method. The bytecode should be invokestatic 
for a static method. This is why the error is an IncompatibleClassChangeError.
Comment 1 Philipe Mulet CLA 2002-01-21 14:19:37 EST 
Adapted to this change for 1.4 mode only.
Fixed