5398570308
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>. |
||
|---|---|---|
| .. | ||
| .settings | ||
| META-INF | ||
| OSGI-INF/l10n | ||
| data | ||
| launchers | ||
| source/com/ibm/wala | ||
| build.gradle | ||
| build.properties | ||
| pom.xml | ||