Bug 75517 - No classpath delta for project becoming exported
Summary: No classpath delta for project becoming exported
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.1 M3   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-02 10:46 EDT by Philipe Mulet CLA
Modified: 2004-10-20 09:09 EDT (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 Philipe Mulet CLA 2004-10-02 10:46:46 EDT 
Build 3.1 M2

When a required project gets exported on the buildpath, no delta gets issued,
even though it should be ADDED|REMOVED or something along this line.

I suspect it comes from the fact originally project CP changes could only occur
due to project being discovered or removed (and these are not to be broadcasted).

Note: if down the road we add inclusion/exclusion patterns to required projects,
these should also be notified when changing.
Comment 1 Jerome Lanneluc CLA 2004-10-08 10:07:30 EDT 
I'm getting the following delta:
		"P2[*]: {CONTENT | CLASSPATH CHANGED}\n" + 
		"	ResourceDelta(/P2/.classpath)[*]"
Do you have steps to reproduce ?
Comment 2 Jerome Lanneluc CLA 2004-10-20 09:09:58 EDT 
Could not reproduce