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
..
.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	Buildship removed classpath provider thing from all launch configs	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
src/com/ibm/wala	Revert "Build WALA using Gradle instead of Maven" (#298)	2018-04-18 12:15:56 -04:00
build.gradle	Have Buildship add Eclipse plugin (PDE) nature to some subprojects	2018-04-18 11:29:25 -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