Ben Liblit decd164fa6 Require JUnit 4.12 instead of 4.11 ... WALA itself does not use any JUnit 4.12 features. However, I am working on a WALA-based project that does require JUnit 4.12. Mixing jar versions is a path to madness. So if the WALA maintainers don't mind, it would make my life easier if WALA itself required JUnit 4.12. Otherwise, I need to maintain that 4.11/4.12 difference indefinitely as a divergence between official WALA and my WALA variant. I suppose an alternative could be to let the JUnit version be specified externally somehow. I have not explored this option in depth, but could look into it if simply moving to JUnit 4.12 is undesirable.		2018-05-21 17:27:54 -05:00
..
.settings	Let Buildship create new settings files when importing	2018-04-18 11:29:25 -05:00
dat	changes for handling of 'callbacks' in dynamic CGs	2015-06-28 17:06:21 -04:00
launchers	Update Eclipse JUnit test launchers for use with Buildship	2018-04-18 11:29:27 -05:00
META-INF	Bump version to 1.5.0-SNAPSHOT before merging with WALA master	2018-04-18 11:29:29 -05:00
src/com/ibm/wala	Don't put fixed-name, writable files into "java.io.tmpdir"	2018-04-18 11:29:29 -05:00
build.gradle	Require JUnit 4.12 instead of 4.11	2018-05-21 17:27:54 -05:00
build.properties	ast-based constant folding	2018-04-28 12:05:49 +02:00
javaCompiler...args	generate linux build file	2008-05-29 15:34:20 +00:00
plugin.properties	complete conversion to Unix line endings	2012-09-04 16:05:49 -07:00
pom.xml	Require JUnit 4.12 instead of 4.11	2018-05-21 17:27:54 -05:00