Make Java convention the composition root

[bric3]

What Does This Do

Move dependency locking and the remaining java_deps.gradle and java_no_deps.gradle composition into dd-trace-java.conventions.java.

Delete the now-unreferenced gradle/java.gradle compatibility aggregator and retain the Spotless regression guard with guidance toward the Java convention.

Motivation

After #12331 migrates the remaining direct consumers, the Java convention can become the composition root and own the incremental extraction of its remaining legacy internals.

See #12258.

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

[datadog-prod-us1-6]

More details

The Java convention keeps the deleted aggregator's plugin and script order. No build script still refers to the deleted file.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit ebc24bc · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}

[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.03 s	13.96 s	[-0.4%; +1.4%] (no difference)
startup:insecure-bank:tracing:Agent	12.95 s	12.99 s	[-1.0%; +0.3%] (no difference)
startup:petclinic:appsec:Agent	16.47 s	16.75 s	[-6.2%; +2.8%] (no difference)
startup:petclinic:iast:Agent	16.83 s	16.89 s	[-1.0%; +0.3%] (no difference)
startup:petclinic:profiling:Agent	16.06 s	16.77 s	[-8.6%; +0.1%] (no difference)
startup:petclinic:sca:Agent	16.74 s	16.53 s	[+0.3%; +2.2%] (maybe worse)
startup:petclinic:tracing:Agent	16.06 s	16.33 s	[-2.7%; -0.6%] (maybe better)

Commit: ebc24bc0 · 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.