WALA/com.ibm.wala.cast.js.test/.launchConfigurations
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
..
WALA-CAst-JS-Test-Downloads.launch Strip execute bits from many non-executable (i.e., non-script) files 2017-02-23 06:10:08 -06:00
com.ibm.wala.cast.js.test-JUnit.launch Update Eclipse JUnit test launchers for use with Buildship 2018-04-18 11:29:27 -05:00