Ben Liblit 89860b53bb Let Buildship create new settings files when importing ... These settings files currently are generated with an initial timestamp comment line, which is not something we'd want to track in version control. Fortunately, the contents of these files are entirely mundane, so there should be no problem with having Buildship generate them anew each time a developer imports WALA into Eclipse as an existing Gradle project.		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
dat	changes for handling of 'callbacks' in dynamic CGs	2015-06-28 17:06:21 -04:00
launchers	Many improvements to Gradle build support, including within Eclipse	2018-04-18 11:29:24 -05: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	Revert "Build WALA using Gradle instead of Maven" (#298)	2018-04-18 12:15:56 -04: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