| Summary: | Compiler warnings in N20101003-2000 | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Olivier Thomann <Olivier_Thomann> |
| Component: | UI | Assignee: | Prakash Rangaraj <prakash> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | prakash |
| Version: | 3.7 | ||
| Target Milestone: | 3.7 M3 | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
Fixed in HEAD Thanks Olivier. As a related question. CocoaUIEnhancer has tons of warnings, so I missed this. How do you find new warnings in the file? Is there an automated way of doing it? (In reply to comment #1) > As a related question. CocoaUIEnhancer has tons of warnings, so I missed this. > How do you find new warnings in the file? Is there an automated way of doing > it? Yes, you check the warnings reported in the build page in the result tests section. |
1. WARNING in /src/org/eclipse/ui/internal/cocoa/CocoaUIEnhancer.java (at line 334) if(workbenchWindow.PROP_COOLBAR_VISIBLE.equals(event.getProperty())) { The static field WorkbenchWindow.PROP_COOLBAR_VISIBLE should be accessed in a static way "workbenchWindow" should be replaced with "WorkbenchWindow".