Declare instrumentation dependencies directly

[bric3]

What Does This Do

Replaces provider-wrapped instrumentation project dependencies with direct ProjectDependency declarations.

It also collects the full paths of projects excluded from the aggregate instrumentation JAR in an explicit set.

Motivation

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.

Additional Notes

This was introduced when work on removing the afterEvaluate in this project.

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Once approved, use merge queue to merge the PR

Jira ticket: [PROJ-IDENT]

[datadog-prod-us1-4]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 69.73% (+12.46%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 42eb19a | Docs | Datadog PR Page | Give us feedback!}

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	14.01 s	13.85 s	[+0.5%; +1.9%] (maybe worse)
startup:insecure-bank:tracing:Agent	12.91 s	13.02 s	[-1.6%; -0.1%] (maybe better)
startup:petclinic:appsec:Agent	16.97 s	16.73 s	[+0.3%; +2.7%] (maybe worse)
startup:petclinic:iast:Agent	16.98 s	16.95 s	[-0.6%; +1.0%] (no difference)
startup:petclinic:profiling:Agent	16.76 s	16.80 s	[-1.3%; +0.8%] (no difference)
startup:petclinic:sca:Agent	16.92 s	16.63 s	[+0.7%; +2.9%] (maybe worse)
startup:petclinic:tracing:Agent	16.07 s	16.07 s	[-0.8%; +0.8%] (no difference)

Commit: 42eb19ae · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

[datadog-prod-us1-4]

More details

The PR successfully refactors dependency declaration from lazy provider-wrapped references to direct ProjectDependency calls, aligning with the established pattern already in use elsewhere in the same file (line 29). The change removes unnecessary indirection without altering the dependency graph or build behavior. No regressions identified.

Was this helpful? React 👍 or 👎

_{📊 Validated against 3 scenarios · Open Bits AI session}

_{🤖 Datadog Autotest · Commit 42eb19a · What is Autotest? · Any feedback? Reach out in #autotest}

[ValentinZakharov]

LGTM

[bric3]

/merge -f --reason="Not affected by additional jobs in MQ"

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-07-17 19:35:25 UTC ℹ️ Start processing command /merge -f --reason="Not affected by additional jobs in MQ"

---

2026-07-17 19:35:29 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 0s (p90).

---

2026-07-17 19:35:39 UTC ℹ️ MergeQueue: This merge request was merged

Warning

This change was merged without running any pre merge CI checks

Reason: Not affected by additional jobs in MQ