Ben Liblit efd3a6ab18 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-17 15:02:35 -05:00
..
.externalToolBuilders	2007 04 12, Naoshi Tabuch: tabee@jp.ibm.com	2007-04-12 05:53:20 +00:00
.settings	Let Buildship create new settings files when importing	2018-04-17 15:02:35 -05:00
META-INF	Many improvements to Gradle build support, including within Eclipse	2018-04-17 15:02:35 -05:00
OSGI-INF/l10n	Externalize bundle names and vendors	2017-06-07 17:42:11 +02:00
data	Initial contribution of core script analysis code	2007-02-02 17:17:13 +00:00
source	WALA uses Git, so CVS ignore patterns are moot	2018-04-14 19:08:14 -05:00
build.gradle	Have Buildship add Eclipse plugin (PDE) nature to some subprojects	2018-04-17 15:02:35 -05:00
build.properties	Externalize bundle names and vendors	2017-06-07 17:42:11 +02:00
mvncentral.xml	Update Maven Central configurations to also use Java 8 (#264)	2017-11-23 12:55:05 -08:00
pom.xml	version 1.4.4-SNAPSHOT	2017-08-06 07:25:20 -07:00