Bug 25995 - Marker for "static method should be accessed in a static way"
Summary: Marker for "static method should be accessed in a static way"
Status: VERIFIED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.1 M3   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 25994 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-11-11 15:00 EST by Vijay Aravamudhan CLA
Modified: 2004-11-05 00:06 EST (History)
0 users

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 Vijay Aravamudhan CLA 2002-11-11 15:00:09 EST 
hi,
In some of my projects, we have code like this:
Toolkit.getDefaultToolkit().getSystemEventQueue().invokeAndWait(new Runnable())

This is the "standard" way of posting an event to the EventQueue. Can this task 
marker be made more intelligent?

I know that we can put in some filters - but that again seems like just a 
workaround, and not a real solution.
Comment 1 Vijay Aravamudhan CLA 2002-11-11 15:02:41 EST 
Another example is:
Thread.currentThread().sleep(1000);
Comment 2 Philipe Mulet CLA 2002-11-11 17:13:15 EST 
I agree for the filtering counter-argument.
Why don't you simply write: Thread.sleep(1000) ?

This warning is optional, you can turn it off in the compiler preferences.
Comment 3 Philipe Mulet CLA 2002-11-11 17:13:40 EST 
*** Bug 25994 has been marked as a duplicate of this bug. ***
Comment 4 Philipe Mulet CLA 2002-11-11 17:15:55 EST 
Is it ok to close?
Comment 5 Philipe Mulet CLA 2002-11-12 09:26:14 EST 
Closing. Option exists if such pattern is meant to be desired.
Comment 6 Philipe Mulet CLA 2002-11-12 09:26:28 EST 
Forgot to assign
Comment 7 Philipe Mulet CLA 2002-11-12 09:27:04 EST 
Closing