DASCA
/
WALA
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
WALA/com.ibm.wala.ide.jsdt.tests/build.gradle

28 lines
723 B
Groovy
Raw Normal View History

Add a resource directory containing a zip archive used for testing The excluded test in this subproject still does not pass, though now it's failing for a different reason than before. Progress, I suppose!
2018-02-14 23:38:44 +00:00
sourceSets.test {
java.srcDirs = ['src']
resources.srcDirs = ['testdata']
}
Many improvements to Gradle build support, including within Eclipse
2017-12-15 19:27:08 +00:00
dependencies {
Clean up some simple syntactic redundancy in dependency declarations
2018-01-11 03:56:27 +00:00
testCompile(
Find Eclipse jars using local Maven mirror of Eclipse P2 repository This should give us a set of mutually-consistent jars rather than picking up random, outdated pieces from Maven Central or wherever else I could find them. We now also have a single, central place where we set the Eclipse version that we're building against. Much, *much* cleaner.
2018-02-14 20:53:56 +00:00
'eclipse-deps:org.eclipse.core.runtime:+',
'eclipse-deps:org.eclipse.equinox.common:+',
'eclipse-deps:org.eclipse.osgi:+',
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 21:37:54 +00:00
'junit:junit:4.12',
Dependency tweaks suggested by Gradle linter I'm starting to wonder whether the linter might be driving us in cycles rather than reaching a fixed point. We should keep our eyes on this.
2018-01-17 18:26:00 +00:00
'org.osgi:org.osgi.core:4.2.0',
Also get Eclipse JSDT from a P2 repository, but not the same one
2018-02-14 21:11:00 +00:00
'wst-deps:org.eclipse.wst.jsdt.core:+',
Clean up some simple syntactic redundancy in dependency declarations
2018-01-11 03:56:27 +00:00
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'),
)
Many improvements to Gradle build support, including within Eclipse
2017-12-15 19:27:08 +00:00
}
Explicitly disable regression tests that are currently failing <https://github.com/liblit/WALA/issues/5> notes that several subprojects' tests are currently broken under Gradle. I'd still like to be able to run non-broken tests, though. So here I'm disabling the failing tests. The intent is to treat these exclusions as a to-do list. We can remove exclusions as we get the corresponding tests working. No more exclusions means <https://github.com/liblit/WALA/issues/5> is fixed.
2018-01-17 20:59:22 +00:00
test {
// https://github.com/liblit/WALA/issues/5
exclude '**/JSProjectScopeTest.class'
}