Bug 7129 - Problems with replacing a project
Summary: Problems with replacing a project
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.0 M2   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 5272 (view as bug list)
Depends on:
Blocks:
 
Reported: 2001-12-20 07:35 EST by Martin Aeschlimann CLA
Modified: 2002-01-11 08:37 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Aeschlimann CLA 2001-12-20 07:35:26 EST
During updating projects using the selfhosting tool, I had problems with a 
JavaModelException coming from setting the classpath, stating that the project 
does not exist. As I just created the project this seemed to be bug.
Can't give a reproducible case but from debugging this is my suspect:

JavaModelManager contains a list fProjectsBeingDeleted.
It is set with JavaModelManager.deleting and removed in 
checkProjectBeingAdded() or deleted

- deleted has no references, seems to be unused
- checkProjectBeingAdded is called in a resource change event.
  as I call everything in a workspacerunnable, this will not be invoked
  before all projects are created.
Comment 1 Martin Aeschlimann CLA 2001-12-20 07:35:45 EST
to jcore
Comment 2 Philipe Mulet CLA 2002-01-07 07:28:02 EST
Pls investigate
Comment 3 Jerome Lanneluc CLA 2002-01-08 07:12:38 EST
The project should have been removed from the list of project being deleted 
before firing the delta. This was not done because only ADDED projects were 
checked. Fixed by checking CHANGED projects as well (this is the case of the 
replace: the project is removed then added and the resulting delta is CHANGED).

Also removed the unused method deleted.
Comment 4 Martin Aeschlimann CLA 2002-01-08 08:57:36 EST
*** Bug 5272 has been marked as a duplicate of this bug. ***