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
..
#com.ibm.wala.ide.jdt.test.launch#	Rename "...-feature" to "..._feature" in subdirs and features	2017-08-30 16:32:33 -05:00
ECJJavaIRTest.launch	Update Eclipse JUnit test launchers for use with Buildship	2018-04-18 11:29:27 -05:00
JDTJava15IRTests.launch	more type parameters for analysis engine	2018-04-10 16:00:44 -04:00
JDTJavaIRTests.launch	further refactoring to enable more reuse	2018-02-05 15:18:37 -08:00