Summary: | Need to trace classpath container initialization failures | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Jerome Lanneluc <jerome_lanneluc> | ||||
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | CC: | daniel_megert, david_audel, Olivier_Thomann, philippe_mulet | ||||
Version: | 3.4 | Flags: | philippe_mulet:
review+
daniel_megert: review+ david_audel: review+ Olivier_Thomann: review+ |
||||
Target Milestone: | 3.4 RC4 | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Jerome Lanneluc
2008-05-30 09:22:30 EDT
Created attachment 102858 [details]
Proposed fix
+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. +1 for RC4. David, Olivier can you please review? +1 Patch looks good: +1. Fix released for 3.4RC4 Verified for 3.4RC4 using I20080606-0100 |