decd164fa6
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.
28 lines
723 B
Groovy
28 lines
723 B
Groovy
sourceSets.test {
|
|
java.srcDirs = ['src']
|
|
resources.srcDirs = ['testdata']
|
|
}
|
|
|
|
dependencies {
|
|
testCompile(
|
|
'eclipse-deps:org.eclipse.core.runtime:+',
|
|
'eclipse-deps:org.eclipse.equinox.common:+',
|
|
'eclipse-deps:org.eclipse.osgi:+',
|
|
'junit:junit:4.12',
|
|
'org.osgi:org.osgi.core:4.2.0',
|
|
'wst-deps:org.eclipse.wst.jsdt.core:+',
|
|
project(':com.ibm.wala.cast'),
|
|
project(':com.ibm.wala.cast.js'),
|
|
project(':com.ibm.wala.cast.js.rhino'),
|
|
project(':com.ibm.wala.core'),
|
|
project(':com.ibm.wala.ide.jsdt'),
|
|
project(':com.ibm.wala.util'),
|
|
project(configuration: 'testArchives', path: ':com.ibm.wala.ide.tests'),
|
|
)
|
|
}
|
|
|
|
test {
|
|
// https://github.com/liblit/WALA/issues/5
|
|
exclude '**/JSProjectScopeTest.class'
|
|
}
|