Community
Participate
Working Groups
If a method is made static, the meaning of a synchronized keyword in the signature changes, so it's not generally safe to let the quick-fix to do the change. Of course accessing only static data in a non-static method and synchronizing on an instance is bad style, but still, the quick-fixes should play it safe.
In case my description wasn't clear enough: Eclipse warns that a method can be made static when the method doesn't access anything non-static. But it fails to recognize the fact that the keyword synchronized actually does access the object instance i.e. something non-static. So the method actually cannot be made static without changing semantics.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
