A comprehensive Java development environment using layered Docker containers.

• OpenJDK 25 (LTS version)
• Maven - Dependency management and build tool
• Gradle 8.5 - Modern build automation
• Spring Boot CLI - Spring application scaffolding
• SDKMan - Java version management

• Git, Docker, and common development utilities (from base layer)
• VS Code Java extension pack support
• Maven and Gradle caching for faster builds
• Persistent M2 repository at /workspace/m2repo
• SonarScanner CLI and SonarQube CLI from the shared devBench base
• JaCoCo CLI/agent plus Maven and Gradle Sonar coverage helpers

• 8080 - Spring Boot default port
• 8081 - Alternative web application port
• 5005 - Java remote debugging port
• 9090 - Metrics/Actuator endpoints

./scripts/build-layer.sh

This will:

• Check for dev-bench-base:latest (build if needed)
• Build the Java-specific layer (java-bench:latest)
• Refresh the user image (java-bench:${USER})

./setup.sh

code .

Then select "Reopen in Container" from the command palette.

• Layer 1 (dev-bench-base): Common development tools
• Layer 2 (java-bench): Java-specific packages and tools

Benefits:

• Faster rebuilds (only Layer 2 changes)
• Shared base across all benches
• Better Docker layer caching

# Create new Maven project
mvn archetype:generate -DgroupId=com.example -DartifactId=my-app

# Build and package
mvn-package  # alias for: mvn clean package

# Run tests
mvn-test

# Create new Gradle project
gradle init

# Build project
gradle-build  # alias for: gradle build

# Run tests
gradle-test

Store SONARQUBE_TOKEN outside .codex, for example in ~/.config/sonarqube/sonar.env. The Java helpers read the same file used by the Codex MCP setup and export SONAR_TOKEN for scanner tools.

For Maven projects, run from the project root:

sonarcloud-java-maven

This runs JaCoCo prepare-agent, verify, JaCoCo report, and the Sonar Maven scanner. The default JaCoCo XML path is target/site/jacoco/jacoco.xml, which SonarCloud detects automatically.

For Gradle projects, the project must apply both plugins:

plugins {
    id "jacoco"
    id "org.sonarqube" version "7.3.1.8318"
}

jacocoTestReport {
    reports {
        xml.required = true
    }
}

Then run:

sonarcloud-java-gradle

This runs test, jacocoTestReport, and ${SONAR_GRADLE_TASK:-sonar} using ./gradlew when it exists, otherwise the system gradle. Set SONAR_GRADLE_TASK=sonarqube for projects that still expose the older task name.

# Create new Spring Boot project
spring init --dependencies=web,data-jpa my-spring-app

# Run Spring Boot application
spring-run  # alias for: ./mvnw spring-boot:run

# List available Java versions
sdk list java

# Install a specific Java version
sdk install java 17.0.9-tem

# Switch Java version
sdk use java 17.0.9-tem

/workspace/
├── projects/      # Your Java projects
├── m2repo/        # Maven repository cache
└── .gradle/       # Gradle cache

Maven is configured to use /workspace/m2repo for the local repository, persisting dependencies across container restarts.

• JAVA_HOME: /usr/lib/jvm/java-25-openjdk-amd64
• GRADLE_HOME: /opt/gradle/gradle-9.6.1
• MAVEN_OPTS: -Dmaven.repo.local=/workspace/m2repo

• mvn-clean - Clean Maven project
• mvn-package - Clean and package
• mvn-install - Clean and install
• mvn-test - Run tests
• mvn-sonar-coverage - Run Maven tests, JaCoCo XML coverage, and Sonar scan
• gradle-build - Build Gradle project
• gradle-clean - Clean Gradle project
• gradle-test - Run Gradle tests
• gradle-sonar-coverage - Run Gradle tests, JaCoCo XML coverage, and Sonar scan
• spring-run - Run Spring Boot app

# Check if image exists
docker images | grep java-bench

# Rebuild Layer 2 and Layer 3 if needed
./scripts/build-layer.sh

# Check Maven settings
cat ~/.m2/settings.xml

# Clear cache if needed
rm -rf /workspace/m2repo/*

# Verify Java version
java -version

# Check JAVA_HOME
echo $JAVA_HOME

• Container Version: 1.0.0
• Base Image: dev-bench-base
• JDK Version: OpenJDK 25
• Maven Version: (from apt)
• Gradle Version: 8.5
• Spring Boot CLI: 3.2.0