Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 326924 - Compiler warnings in N20101003-2000
Summary: Compiler warnings in N20101003-2000
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: 3.7 M3   Edit
Assignee: Prakash Rangaraj CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-04 10:03 EDT by Olivier Thomann CLA
Modified: 2010-10-05 08:40 EDT (History)
1 user (show)

See Also:

Attachments
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 Olivier Thomann CLA 2010-10-04 10:03:48 EDT 
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".
Comment 1 Prakash Rangaraj CLA 2010-10-05 00:16:03 EDT 
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?
Comment 2 Olivier Thomann CLA 2010-10-05 08:40:04 EDT 
(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.