Ben Liblit dd1f51e8f0 Buildship removed classpath provider thing from all launch configs ... This consistently happens when I import WALA as an existing Gradle project into Eclipse with Buildship. I don't really know what this change means, or whether it's desirable. For now, I'm going to trust Buildship and see what happens.		2018-04-18 11:29:25 -05:00
..
.launchConfigurations	Buildship removed classpath provider thing from all launch configs	2018-04-18 11:29:25 -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	Simplify loading of plugins shared by many subprojects	2018-04-18 11:29:25 -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