[BUG] Maven/Gradle builds fail in Claude Code Web cloud environment - DNS resolution failure for repo.maven.apache.org

Open 💬 12 comments Opened Dec 8, 2025 by axel-nyman

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Maven and Gradle builds fail in Claude Code Web's cloud environment when attempting to download dependencies from Maven Central. The build fails with a DNS resolution error for repo.maven.apache.org, despite the documentation explicitly listing "JVM: Maven Central, Gradle services" as allowed domains under the package managers allowlist.

This completely blocks Java/Maven development in Claude Code Web.

What Should Happen?

Maven should be able to download dependencies from repo.maven.apache.org (Maven Central) as documented in the allowlist at https://code.claude.com/docs/en/claude-code-on-the-web

Error Messages/Logs

Downloading from central: https://repo.maven.apache.org/maven2/org/springframework/boot/spring-boot-starter-parent/3.4.11/spring-boot-starter-parent-3.4.11.pom
[FATAL] Non-resolvable parent POM for com.template:spring-boot-rest-api-template:1.0.0-SNAPSHOT:
The following artifacts could not be resolved: org.springframework.boot:spring-boot-starter-parent:pom:3.4.11 (absent):
Could not transfer artifact org.springframework.boot:spring-boot-starter-parent:pom:3.4.11 from/to central (https://repo.maven.apache.org/maven2):
repo.maven.apache.org: Temporary failure in name resolution

Steps to Reproduce

  1. Open any Java/Maven project in Claude Code Web (cloud sandbox)
  2. Run ./mvnw test or ./mvnw compile
  3. Observe DNS resolution failure for repo.maven.apache.org

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Claude Code Web

Platform

Other

Operating System

Other Linux

Terminal/Shell

Other

Additional Information

Similar Issue - Now Fixed

This is similar to #10307 where crates.io (Rust) was blocked despite being documented as allowed. That issue was fixed by adding domains to the NO_PROXY environment variable.

Potential Solution

Add Maven Central domains to NO_PROXY (similar to crates.io fix): repo.maven.apache.org, *.maven.apache.org, repo1.maven.org

Affected Package Managers

  • Java: Maven, Gradle
  • Potentially other JVM languages (Kotlin, Scala) using Maven Central

References

View original on GitHub ↗

This issue has 12 comments on GitHub. Read the full discussion on GitHub ↗