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
META-INF	Require JUnit 4.12 instead of 4.11	2018-05-21 17:27:54 -05:00
OSGI-INF/l10n	Externalize bundle names and vendors	2017-06-07 17:42:11 +02:00
data	dalvik test infrastructure	2015-04-05 21:22:55 -04:00
source/com/ibm/wala/dalvik	further refactoring to enable more reuse	2018-02-05 15:18:37 -08:00
.gitignore	Ignore a transient file that appears during testing	2018-04-18 11:29:27 -05:00
build.gradle	Require JUnit 4.12 instead of 4.11	2018-05-21 17:27:54 -05:00
build.properties	java 8 changes	2017-08-25 10:58:00 -04:00
build.xml	try to find dx.jar	2018-02-05 15:43:49 -08:00
pom.xml	Require JUnit 4.12 instead of 4.11	2018-05-21 17:27:54 -05:00