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	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	NodeJS Support, including Ant build script to download Nodejs Core Library files	2016-10-27 16:37:33 +02:00
src/com/ibm/wala/cast/js/nodejs	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	refactoring of CAst front end machinery to allow more reuse	2018-01-25 14:42:27 -05:00
build.xml	Various fixes to nodejs project config files	2017-06-23 07:01:18 +02:00
pom.xml	Revert "Build WALA using Gradle instead of Maven" (#298)	2018-04-18 12:15:56 -04:00