Avoid Maven Central fallback in build setup

[AlexeyKuznetsov-DD]

What Does This Do

Avoids adding explicit Maven Central repositories when a Maven proxy is configured. Gradle Plugin Portal remains enabled for plugin markers.

Motivation

Temporary workaround for Maven Central rate limiting during dependency-cache population.

Additional Notes

Follow-up to #12403. Plugin repository handling remains unchanged because the configured proxy does not resolve every plugin marker.

Validation: ./gradlew help and ./gradlew spotlessKotlinGradleCheck

Contributor Checklist

Required labels are applied.

Jira ticket: [N/A]

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-04T01:42:52.584953Z	c55f6c1	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c55f6c1ed6

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[datadog-datadog-prod-us1]

An empty exported proxy property now disables its public repository fallback. This can stop dependency or plugin resolution in CI jobs that do not set the proxy variables.

_{Open Bits AI session}

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

[datadog-datadog-prod-us1]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 59.03% (-0.04%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: c868a95 | Docs | View more details | 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.81 s	14.83 s	[-0.9%; +0.7%] (no difference)
startup:insecure-bank:tracing:Agent	13.54 s	13.71 s	[-1.9%; -0.5%] (maybe better)
startup:petclinic:appsec:Agent	16.88 s	16.80 s	[-0.7%; +1.6%] (no difference)
startup:petclinic:iast:Agent	16.77 s	16.93 s	[-1.7%; -0.3%] (maybe better)
startup:petclinic:profiling:Agent	16.64 s	16.68 s	[-1.3%; +0.9%] (no difference)
startup:petclinic:sca:Agent	16.86 s	15.92 s	[+1.5%; +10.3%] (significantly worse)
startup:petclinic:tracing:Agent	15.65 s	16.01 s	[-6.4%; +1.8%] (no difference)

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

[bric3]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-09-04 07:54:32 UTC ℹ️ Start processing command /merge

---

2026-09-04 07:54:41 UTC ℹ️ MergeQueue: Pull request is not mergeable yet

It will be processed automatically as soon as GitHub reports it as mergeable. View in MergeQueue UI.

• Run /code blockers to see what is blocking it.
• Run /remove to cancel it.

---

2026-09-04 08:41:23 UTC ℹ️ MergeQueue: merge request added to the queue

The expected merge time in master is approximately 1h (p90).

---

2026-09-04 09:49:00 UTC ℹ️ MergeQueue: This merge request was merged