WALA/com.ibm.wala.ide.jsdt.tests/.settings
Ben Liblit e1d2fa9850 Suppress Eclipse warnings about potentially-static methods
The "potentially" qualifier is here because these methods are visible
outside the WALA source tree.  These methods may seem OK to be static
based on the code we have here, but we have no way of knowing whether
third-party code expected to be able to subclass and override.  I'm
going to play it safe and assume that we want to allow that.

Note that we are still allowing Eclipse warnings about methods that
can *definitely* be declared static; a different configuration option
controls these.  For private methods, final methods, and methods in
final classes, if the code seems static-safe based on what we have
here, then that's good enough: we don't need to worry about
third-party overrides.
2017-06-07 08:29:23 -07:00
..
org.eclipse.jdt.core.prefs Suppress Eclipse warnings about potentially-static methods 2017-06-07 08:29:23 -07:00
org.eclipse.pde.prefs Disable Eclipse warnings about missing version constraints 2017-03-28 20:37:41 -05:00
org.eclipse.wst.validation.prefs Merge branch 'master' into warning-fixes-xml-validation 2016-11-29 10:08:00 -06:00