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	WALA uses Git, so CVS ignore patterns are moot	2018-04-14 19:08:14 -05:00
lib	remove dependency from slf4j logger in wala.core project	2014-07-30 15:44:17 +02:00
src/com/ibm/wala	Revert "Build WALA using Gradle instead of Maven" (#298)	2018-04-18 12:15:56 -04:00
antbuild.properties	trying to update build.xml	2010-05-21 16:28:13 +00: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:30:59 +00:00
mvncentral.xml	Revert "Build WALA using Gradle instead of Maven" (#298)	2018-04-18 12:15:56 -04:00
plugin.properties	Match case of property names to that expected in manifest	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