Bug 15690 - Classpath being set in wrong notification lifecycle
Summary: Classpath being set in wrong notification lifecycle
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 M6   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-09 19:17 EDT by Rodrigo Peretti CLA
Modified: 2020-05-24 23:44 EDT (History)
1 user (show)

See Also:

Attachments
log file (23.30 KB, text/plain)
2002-05-09 19:18 EDT, Rodrigo Peretti CLA 		no flags Details
View All 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 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.