Bug 234848 - Need to trace classpath container initialization failures
Summary: Need to trace classpath container initialization failures
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.4 RC4   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-30 09:22 EDT by Jerome Lanneluc CLA
Modified: 2008-06-06 09:03 EDT (History)
4 users (show)

See Also:
philippe_mulet: review+
daniel_megert: review+
david_audel: review+
Olivier_Thomann: review+


Attachments
Proposed fix (15.81 KB, patch)
2008-05-30 10:00 EDT, Jerome Lanneluc CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Jerome Lanneluc CLA 2008-05-30 09:22:30 EDT
I20080529-1806

To help debugging bugs such as bug 232478, we should have a tracing mode where failures during the classpath container initialization are logged.
Comment 1 Jerome Lanneluc CLA 2008-05-30 10:00:07 EDT
Created attachment 102858 [details]
Proposed fix
Comment 2 Philipe Mulet CLA 2008-05-30 10:05:14 EDT
+1 for RC4.
The change looks really safe, since it only provides a new mode for activating existing trace functionality to help diagnosing buildpath init failures (regular trace is just too verbose).

There are timing issues near buildpath inits which have not been understood yet, it would be good to at least be able to collect tracing information from users.
Comment 3 Dani Megert CLA 2008-05-30 10:34:45 EDT
+1 for RC4.
Comment 4 Jerome Lanneluc CLA 2008-05-30 10:39:02 EDT
David, Olivier can you please review?
Comment 5 Olivier Thomann CLA 2008-05-30 11:26:13 EDT
+1
Comment 6 David Audel CLA 2008-06-02 04:17:48 EDT
Patch looks good: +1.
Comment 7 Jerome Lanneluc CLA 2008-06-02 05:18:10 EDT
Fix released for 3.4RC4
Comment 8 Frederic Fusier CLA 2008-06-06 09:03:23 EDT
Verified for 3.4RC4 using I20080606-0100