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
dat	changes for handling of 'callbacks' in dynamic CGs	2015-06-28 17:06:21 -04:00
launchers	Update Eclipse JUnit test launchers for use with Buildship	2018-04-18 11:29:27 -05:00
META-INF	Revert "Build WALA using Gradle instead of Maven" (#298)	2018-04-18 12:15:56 -04:00
src/com/ibm/wala	Revert "Build WALA using Gradle instead of Maven" (#298)	2018-04-18 12:15:56 -04:00
build.gradle	Note some excessive resource copying that we should eventually fix	2018-04-18 11:29:27 -05:00
build.properties	Tweak output dirs to match what Buildship puts into ".classpath"	2018-04-18 11:29:25 -05:00
javaCompiler...args	generate linux build file	2008-05-29 15:34:20 +00:00
plugin.properties	complete conversion to Unix line endings	2012-09-04 16:05:49 -07:00
plugin.xml	Add stub DOCTYPE declarations for Eclipse plug-in manifest files	2016-11-28 14:55:34 -06:00
pom.xml	Revert "Build WALA using Gradle instead of Maven" (#298)	2018-04-18 12:15:56 -04:00