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.
40 lines
1.1 KiB
Groovy
40 lines
1.1 KiB
Groovy
sourceSets.test {
|
|
java.srcDirs = ['source']
|
|
resources.srcDirs = ['testdata']
|
|
}
|
|
|
|
dependencies {
|
|
testCompile(
|
|
'eclipse-deps:org.eclipse.core.runtime:+',
|
|
'eclipse-deps:org.eclipse.jdt.core:+',
|
|
'eclipse-deps:org.eclipse.osgi:+',
|
|
'junit:junit:4.12',
|
|
'org.osgi:org.osgi.core:4.2.0',
|
|
project(':com.ibm.wala.cast'),
|
|
project(':com.ibm.wala.cast.java'),
|
|
project(':com.ibm.wala.cast.java.ecj'),
|
|
project(':com.ibm.wala.core'),
|
|
project(':com.ibm.wala.ide'),
|
|
project(':com.ibm.wala.ide.jdt'),
|
|
project(':com.ibm.wala.shrike'),
|
|
project(':com.ibm.wala.util'),
|
|
project(configuration: 'testArchives', path: ':com.ibm.wala.cast.java.test'),
|
|
project(configuration: 'testArchives', path: ':com.ibm.wala.core.tests'),
|
|
project(configuration: 'testArchives', path: ':com.ibm.wala.ide.tests'),
|
|
)
|
|
testRuntime(
|
|
'eclipse-deps:org.eclipse.core.contenttype:+',
|
|
'eclipse-deps:org.eclipse.equinox.preferences:+',
|
|
)
|
|
}
|
|
|
|
test {
|
|
maxHeapSize = '1200M'
|
|
|
|
// https://github.com/liblit/WALA/issues/5
|
|
exclude '**/JDTJava15IRTests.class'
|
|
exclude '**/JDTJavaIRTests.class'
|
|
|
|
workingDir project(':com.ibm.wala.cast.java.test.data').projectDir
|
|
}
|