Bug 15690

Summary: Classpath being set in wrong notification lifecycle
Product: [Eclipse Project] JDT Reporter: Rodrigo Peretti <rodrigo>
Component: CoreAssignee: Philipe Mulet <philippe_mulet>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: achaninusa
Version: 2.0   
Target Milestone: 2.0 M6   
Hardware: PC   
OS: Windows 2000   
Whiteboard:
Attachments:
Description Flags
log file none

Description Rodrigo Peretti CLA 2002-05-09 19:17:48 EDT 
build 20020508

1) I have an old workspace (it is small and available upon request).
2) Set -data to point to this workspace
3) Eclipse starts and I select all projects and do a refresh
4) No problem shows up in the UI but there is an exception being printed to 
the console (-consolelog)
5) Will attach the log

The problem seems to be trying to update the classpath in the wrong workspace 
notification lifecycle.
Comment 1 Rodrigo Peretti CLA 2002-05-09 19:18:18 EDT 
Created attachment 784 [details]
log file
Comment 2 Philipe Mulet CLA 2002-05-13 06:38:26 EDT 
Problem is that variable initializer is running during post_change 
notification, and thus causing some grief.

Changed the implementation so as to avoid attempting to rewrite the .classpath 
file if in the middle of provessing a post-change event.

Fixed.
Comment 3 Arthur Chan CLA 2020-05-24 23:44:51 EDT 
My eclipse detail:
Version: 2020-03 (4.15.0)
Build id: 20200313-1211
Windows 10


After starting eclipse, the IDE keeps looping thru the "sending classpath notification: and the session becomes unresponsive. 

This happened just last week, prior, my IDE was working well.