Ben Liblit 1d27ca974b Upgrade raw-types-usage warnings to errors where possible ... In general, these diagnostics are now errors in projects for which all such warnings have been fixed. There are three unfixed warnings in two projects, so this diagnostic remains a warning (not an error) in those projects. There are also many places where rwa-types-usage warnings have been locally suppressed using @SuppressWarnings annotations. I haven't systematically revisited those to see if any can be fixed properly. So for those projects this diagnostic must also remain a warning (not an error), since @SuppressWarnings does not work on things Eclipse is configured to treat as errors.		2017-07-12 10:39:06 -07:00
..
org.eclipse.jdt.core.prefs	Upgrade raw-types-usage warnings to errors where possible	2017-07-12 10:39:06 -07:00
org.eclipse.jdt.ui.prefs	rename com.ibm.wala.cast.java.jdt.test to com.ibm.wala.ide.jdt.test	2013-03-30 11:40:18 -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