Bug 3429 - Incremental compilation bug on namespace change in private local class (1GKXC3I)
Summary: Incremental compilation bug on namespace change in private local class (1GKXC3I)
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: All Windows NT
: P3 normal (vote)
Target Milestone: 2.0 M1   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 22:54 EDT by John Arthorne CLA
Modified: 2002-01-14 11:08 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 John Arthorne CLA 2001-10-10 22:54:58 EDT
From "Grenady" on Eclipse Corner:

package packagea;
public class classa {
	int counter = 3;
	private class korna99 {
		public int getInt2() {
			return ++counter+12;
		}
	}
	public int produceInt() {
		return new korna99().getInt2();
	}
}

package packageb;
import packagea.*;
public class classb {
	public void consumeI2nt(classa obj) {
		System.out.println(obj.produceInt());
	}
}

The bug is that if the name of Korna99 is changed, classb gets compiled, even though it has no reference to that type.

NOTES:
Comment 1 Kent Johnson CLA 2001-12-10 16:34:03 EST
classb is dependent on the structure of classa which has changed because its 
member class was renamed.

The new builder does not remember fine grain dependencies to reduce the memory 
footprint