WALA/com.ibm.wala.ide.jsdt.tests
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
..
.settings Suppress Eclipse warnings about potentially-static methods 2017-06-07 08:29:23 -07:00
META-INF update version to 1.4.3-SNAPSHOT 2017-04-19 09:19:09 -07:00
launchers cross-cutting changes to make more of WALA runnable with TeaVM. The biggest change is refactoring to AnalysisCache and friends; since TeaVM does not support SoftReference, I needed to add a layer of interfaces so that I can use a more simpleminded caching implementation for TeaVM. There are other changes to Module and friends to break connections with File and URL, which also cause TeaVM grief. I also organized imports in many places to remove unused types that caused trouble. 2017-02-02 20:33:27 -05:00
src/com/ibm/wala/ide/jsdt/tests Add @Override annotations to all methods that do override (#180) 2017-05-15 07:15:00 -07:00
testdata add ignore file 2013-08-08 10:23:51 -07:00
.classpath fixes to regression tests: 2015-03-24 21:51:35 -04:00
.project Create new project com.ibm.wala.ide.jsdt.tests. 2012-11-28 12:09:55 -05:00
build.properties Fix warnings about unset javacProjectSettings build entries (#176) 2017-05-04 11:44:32 -07:00
pom.xml update version to 1.4.3-SNAPSHOT 2017-04-19 09:19:09 -07:00