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
..
.launchConfigurations	Update Eclipse JUnit test launchers for use with Buildship	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
harness-src/com/ibm/wala/cast/js/test	Use Iterator2Iterable helper to convert more loops to for-each	2017-12-04 14:04:39 -08:00
build.gradle	Change archive file names while unpacking, rather than in two stages	2018-04-18 11:29:26 -05:00
build.properties	Externalize bundle names and vendors	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