This is an automated email from the ASF dual-hosted git repository.

jojochuang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ozone.git


The following commit(s) were added to refs/heads/master by this push:
     new 10b5015f64d HDDS-16968. Update stale Java 8 references in AGENTS.md 
(#11507)
10b5015f64d is described below

commit 10b5015f64d7bc7fe1ee9941e563941d4521c754
Author: Siyao Meng <[email protected]>
AuthorDate: Wed Oct 14 16:36:37 2026 -0700

    HDDS-16968. Update stale Java 8 references in AGENTS.md (#11507)
    
    Generated-by: Claude Opus 5.5 <[email protected]>
    Generated-by: Cursor <[email protected]>
---
 AGENTS.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/AGENTS.md b/AGENTS.md
index 85d66a0fa92..41de8a14ca7 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -22,7 +22,8 @@ Apache Ozone is a multi-module Maven project. The root 
coordinates and version l
 
 Tech stack:
 
-- Java 8 bytecode with JDK 21 runtime compatibility (see the `[21,]` profile 
in `pom.xml`)
+- Java 17 by default (`ozone.java.version.server` in `pom.xml`). Modules that 
set `maven.compiler.release` to
+  `${ozone.java.version.client}` in their own `pom.xml` still target Java 8.
 - Maven build
 - Hadoop RPC and gRPC over Protobuf
 - RocksDB for persistent metadata
@@ -52,7 +53,8 @@ server-side handling, client translation code, and 
integration tests.
 
 ## Local Environment
 
-- Use a JDK 21 runtime locally. Source and target compatibility remain Java 8.
+- Use a JDK 21 runtime locally. Before using Java 9+ syntax or 
standard-library APIs, check the module's
+  `maven.compiler.release` in its `pom.xml`; Maven `--release` governs both 
language level and API surface.
 - Ozone formatting conventions are shared through `.editorconfig`.
 - If Maven behaves unexpectedly, check `java -version` and `mvn -version` 
first.
 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to