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	Bump version to 1.5.0-SNAPSHOT before merging with WALA master	2018-04-18 11:29:29 -05:00
OSGI-INF/l10n	Externalize bundle names and vendors	2017-06-07 17:42:11 +02:00
src/com/ibm/wala/cast/js/nodejs/test	Escape "<" and ">" in Javadoc when not used as HTML tag syntax	2017-12-19 16:53:52 -06:00
testdata	NodeJS Support, including Ant build script to download Nodejs Core Library files	2016-10-27 16:37:33 +02:00
build.gradle	Require JUnit 4.12 instead of 4.11	2018-05-21 17:27:54 -05:00
build.properties	Add missing output directories	2017-06-07 17:42:11 +02:00
pom.xml	Require JUnit 4.12 instead of 4.11	2018-05-21 17:27:54 -05:00