Summary: | Invalid classpath header messages should be logged in verbose mode only | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Olivier Thomann <Olivier_Thomann> | ||||
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | CC: | david_audel, jeffmcaffer | ||||
Version: | 3.4 | ||||||
Target Milestone: | 3.5 M3 | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | |||||||
Bug Depends on: | 250946 | ||||||
Bug Blocks: | |||||||
Attachments: |
|
Description
Olivier Thomann
2008-10-27 16:13:42 EDT
I think we should not even log this problem. Maybe only in tracing mode (when JavaModelManager.CP_RESOLVE_VERBOSE is true). What do you think? I agree. We should not log issues that the user cannot fix. My concern here was that it is not possible to get rid of the warning right now or I missed the option to do so. *** Bug 252364 has been marked as a duplicate of this bug. *** (In reply to comment #2) > I agree. Changing title accordingly Created attachment 116361 [details]
Proposed fix and regression test
Fix and test released for 3.5M3 Verified for 3.5M3 using I20081028-2000 build. |