Ben Liblit 5398570308 Update Eclipse JUnit test launchers for use with Buildship ... Previously Buildship removed its classpath from all of these launchers. Now it's automatically putting that back in as soon as I visit each launcher in Eclipse's "Run Configurations" dialog. Not sure what's going on here, but it certainly seems more sane to me to assume that the Buildship-computed classpath *is* needed for all of these. I have an open question on the Gradle discussion forum to try to understand what's going on here and how to fix it: <https://discuss.gradle.org/t/launchers-lose-buildship-classpath-on-import-regain-it-later/25641>.		2018-04-18 11:29:27 -05:00
..
.settings	Let Buildship create new settings files when importing	2018-04-18 11:29:25 -05:00
META-INF	Revert "Build WALA using Gradle instead of Maven" (#298)	2018-04-18 12:15:56 -04:00
OSGI-INF/l10n	Externalize bundle names and vendors	2017-06-07 17:42:11 +02:00
launchers	Update Eclipse JUnit test launchers for use with Buildship	2018-04-18 11:29:27 -05:00
src/com/ibm/wala/ide/jsdt/tests	Remove "throws XYZ" declarations where XYZ cannot be thrown	2017-07-28 10:20:28 -07:00
testdata	add ignore file	2013-08-08 10:23:51 -07:00
build.gradle	Explicitly disable regression tests that are currently failing	2018-04-18 11:29:26 -05:00
build.properties	Add missing output directories	2017-06-07 17:42:11 +02:00
pom.xml	Revert "Build WALA using Gradle instead of Maven" (#298)	2018-04-18 12:15:56 -04:00