From 42eb19aebf854241fd112c915a6262f886b5b0e5 Mon Sep 17 00:00:00 2001 From: Brice Dutheil Date: Fri, 17 Jul 2026 18:50:30 +0200 Subject: [PATCH] refactor: declare instrumentation dependencies directly Instrumentation project paths are already known during configuration. Wrapping `project(...)` in `providers.provider` adds unnecessary indirection without providing useful laziness. Declaring project dependencies directly makes the aggregation logic clearer and keeps compile-only stub projects out of the resulting JAR. # Conflicts: # dd-java-agent/instrumentation/build.gradle --- dd-java-agent/instrumentation/build.gradle | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/dd-java-agent/instrumentation/build.gradle b/dd-java-agent/instrumentation/build.gradle index 42dc06fcb7d..4b2b6588492 100644 --- a/dd-java-agent/instrumentation/build.gradle +++ b/dd-java-agent/instrumentation/build.gradle @@ -90,9 +90,10 @@ subprojects { Project subProj -> if (subProj.path != ':dd-java-agent:instrumentation:vertx:vertx-redis-client:vertx-redis-client-stubs' && subProj.path != ':dd-java-agent:instrumentation:tibco-businessworks:tibco-businessworks-stubs') { // don't include the redis or tibco stubs - parent_project.dependencies { - addProvider("implementation", providers.provider { project(subProj.path) }) - } + parent_project.dependencies.add( + "implementation", + parent_project.dependencies.project(path: subProj.path) + ) } }