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
OSGI-INF/l10n	Externalize bundle names and vendors	2017-06-07 17:42:11 +02:00
src/com/ibm/wala/cast/js/html/nu_validator	Fix all Eclipse warnings about unnecessary semicolons	2017-07-14 22:39:01 -07:00
tests/com/ibm/wala/cast/js/test	add missing copyright headers	2013-05-22 15:39:19 -07:00
build.gradle	Clean up some simple syntactic redundancy in dependency declarations	2018-04-18 11:29:25 -05:00
build.properties	java 8 changes	2017-08-25 10:58:00 -04:00
pom.xml	Revert "Build WALA using Gradle instead of Maven" (#298)	2018-04-18 12:15:56 -04:00