Ben Liblit fb9042d3a6 Activate more Eclipse diagnostics, and treat many warnings as errors ... The additional diagnostics are ones that were previously being ignored, but which we seem to have been ignoring by default rather than as a conscious choice. For diagnostics of which we currently have *zero* instances, treat these as errors rather than merely warnings. The intent is to permanently lock out future regressions of things we've completely fixed. In the future, whenever we fix the last instance of a given warning in a given Eclipse project, we should also promote that diagnostic to an error to keep things clean into the future.		2017-06-26 11:16:09 -07:00
..
.settings	Activate more Eclipse diagnostics, and treat many warnings as errors	2017-06-26 11:16:09 -07:00
META-INF	Export all packages	2017-06-07 17:42:11 +02:00
OSGI-INF/l10n	Externalize bundle names and vendors	2017-06-07 17:42:11 +02:00
source/com/ibm/wala	Declare private methods static wherever possible	2017-06-07 08:29:23 -07:00
.classpath	scandriod merge	2014-10-01 21:32:36 -04:00
.project	more JS stuff	2012-08-22 12:15:46 -04:00
build.properties	Externalize bundle names and vendors	2017-06-07 17:42:11 +02:00
pom.xml	update version to 1.4.3-SNAPSHOT	2017-04-19 09:19:09 -07:00