DASCA
/
WALA
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
WALA/com.ibm.wala.cast.java.test/build.gradle

26 lines
526 B
Groovy
Raw Normal View History

Load plugins using "plugins" closure rather than "apply plugin" Apparently the latter is considered a "legacy method": <https://docs.gradle.org/current/userguide/plugins.html#sec:old_plugin_application>.
2018-05-23 21:44:29 +00:00
plugins {
id 'com.github.hauner.jarTest'
id 'eclipse'
}
Have Buildship add Eclipse plugin (PDE) nature to some subprojects Specifically, we need this for subprojects that build included plugins for any of the "*_feature" subprojects.
2018-01-15 04:50:52 +00:00
eclipse.project.natures 'org.eclipse.pde.PluginNature'
Properly distinguish main from test code, now that I know how
2017-12-21 15:09:27 +00:00
Replace source directories rather than appending to them I was confused about the differences among: srcDir 'foo' srcDirs ['foo'] srcDirs = ['foo'] As it turns out, the first two append to the set of source directories, while the last replaces this set entirely. I generally want replacement, since WALA's current directory layout never matches Gradle's assumed defaults.
2017-12-26 21:54:35 +00:00
sourceSets.test.java.srcDirs = ['src']
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(
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',
Clean up some simple syntactic redundancy in dependency declarations
2018-01-11 03:56:27 +00:00
'org.osgi:org.osgi.core:4.2.0',
project(':com.ibm.wala.cast'),
project(':com.ibm.wala.cast.java'),
project(':com.ibm.wala.core'),
project(':com.ibm.wala.shrike'),
project(':com.ibm.wala.util'),
project(configuration: 'testArchives', path: ':com.ibm.wala.core.tests'),
)
Many improvements to Gradle build support, including within Eclipse
2017-12-15 19:27:08 +00:00
}
Replicate Maven's heap size limits for tests
2018-01-17 23:37:16 +00:00
test {
maxHeapSize = '800M'
}