Create a "testing" subproject for faster recompilation (#3246)

This is another instance of a grouping of code that is frequently used and
referred to, but infrequently changed. If it's part of the same
compilation unit as core, then it'll need to get recompiled every time
but if we move it out into a different project we won't need to

Also moves some utility classes (required by testing) from util to
common, and removes the unnecessary core:testJar task
This commit is contained in:
gbrodman
2026-10-07 17:58:24 +00:00
committed by GitHub
parent a6bb0a48f5
commit d1e895c46b
71 changed files with 1144 additions and 904 deletions
+10 -8
View File
@@ -52,14 +52,16 @@ tasks.test.finalizedBy jacocoTestReport
configurations {
deploy_jar.extendsFrom runtimeClasspath
matching {
it.name in ['runtimeClasspath', 'compileClasspath']
}.all {
// JUnit is from org.apache.beam:beam-runners-google-cloud-dataflow-java
exclude group: 'junit'
// Mockito is from org.apache.beam:beam-runners-google-cloud-dataflow-java
// See https://issues.apache.org/jira/browse/BEAM-8862
exclude group: 'org.mockito', module: 'mockito-core'
if (project.name != 'testing') {
matching {
it.name in ['runtimeClasspath', 'compileClasspath']
}.all {
// JUnit is from org.apache.beam:beam-runners-google-cloud-dataflow-java
exclude group: 'junit'
// Mockito is from org.apache.beam:beam-runners-google-cloud-dataflow-java
// See https://issues.apache.org/jira/browse/BEAM-8862
exclude group: 'org.mockito', module: 'mockito-core'
}
}
all {
// log4j has high-profile security vulnerabilities. It's a transitive