Ben Liblit 310ef1daa5 Exclude Eclipse ".project" and ".classpath" from version control ... Apparently Buildship generates these when one uses Import -> Existing Gradle Project: <https://discuss.gradle.org/t/buildship-eclipse-plug-in-multiproject-builds/24030/5>. We can use the Gradle "eclipse" plugin if customizations are necessary, but my impression is that the intent is to treat ".project" and ".classpath" as generated files, not sources to be tracked in source control.		2018-04-18 11:29:25 -05:00
..
.externalToolBuilders	Revert "Build WALA using Gradle instead of Maven" (#298)	2018-04-18 12:15:56 -04:00
.settings	Many improvements to Gradle build support, including within Eclipse	2018-04-18 11:29:24 -05:00
META-INF	Many improvements to Gradle build support, including within Eclipse	2018-04-18 11:29:24 -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	Revert "Build WALA using Gradle instead of Maven" (#298)	2018-04-18 12:15:56 -04:00
build.gradle	Fill the dynamic library path for OSX	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
mvncentral.xml	Revert "Build WALA using Gradle instead of Maven" (#298)	2018-04-18 12:15:56 -04:00
pom.xml	Revert "Build WALA using Gradle instead of Maven" (#298)	2018-04-18 12:15:56 -04:00