Bug 49986

Summary: setRawClasspath(...) should fire a F_CLASSPATH_CHANGED delta
Product: [Eclipse Project] JDT Reporter: Jerome Lanneluc <jerome_lanneluc>
Component: CoreAssignee: Jerome Lanneluc <jerome_lanneluc>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: erich_gamma
Version: 3.0   
Target Milestone: 3.0 M8   
Hardware: PC   
OS: Windows 2000   
Whiteboard:

Description Jerome Lanneluc CLA 2004-01-14 10:14:01 EST 
Build 20041013

As described in bug 38513, calling IJavaProject.setRawClasspath(...) currently 
fires no delta when the resolved classpath is the same. It should always fire a 
F_CLASSPATH_CHANGED delta if the raw classpath has changed. This new flag would 
be attached to an IJavaProject delta.
Comment 1 Philipe Mulet CLA 2004-03-01 12:48:00 EST 
Tentatively assigning for M8. I think the flag should describe a raw classpath 
change in general, where the root change would represent the resolved classpath 
change (which there could be none).
Comment 2 Jerome Lanneluc CLA 2004-03-02 13:31:05 EST 
Flag added. It is set when the raw classpath of a project changes.
Comment 3 Erich Gamma CLA 2004-03-15 10:49:55 EST 
I was expecting to get a delta with the F_CLASSPATH_CHANGED flag in the 
following scenario:

1) fresh workspace
2) create a new Java project
3) open the build path property page and add the Required Plug-ins library.

In this case the build class path changes and the following delta is reported:

org.eclipse.jdt.core.ElementChangedEvent[source=Java Model[*]: {CHILDREN}
	Foo[*]: {CONTENT}
		ResourceDelta(/Foo/.classpath)[*]]

notice the the flag isn't F_CLASSPATH_CHANGED in the delta.
Comment 4 Jerome Lanneluc CLA 2004-03-17 18:28:55 EST 
Missed the case of adding an empty classpath container. Sorry.
Fixed and added regression test ClasspathTests.testEmptyContainer()
Comment 5 Frederic Fusier CLA 2004-03-25 10:59:54 EST 
Verified for 3.0 using build I200403250800.