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
..
.launchConfigurations	launch configurations for download scripts	2007-02-08 20:35:39 +00: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
dat	Strip execute bits from many non-executable (i.e., non-script) files	2017-02-23 06:10:08 -06:00
source/com/ibm/wala/cast/js	Revert "Build WALA using Gradle instead of Maven" (#298)	2018-04-18 12:15:56 -04:00
build.gradle	Clean up some simple syntactic redundancy in dependency declarations	2018-04-18 11:29:25 -05:00
build.properties	Add missing output directories	2017-06-07 17:42:11 +02: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