You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the issues of this repository and believe that this is not a duplicate.
I am willing to try to fix this bug myself.
Ⅰ. Issue Description
The console module uses java.net.http.HttpClient (introduced in Java 11), but the module is compiled with Java 8 compatibility settings inherited from the parent POM. This causes compilation errors when running in IDEA.
Ⅱ. Describe what happened
When running the console module in IDEA, a compilation error related to java.net.http.HttpClient occurs:
video
iShot_2026-07-24_13.09.05.mp4
Root Cause Analysis:
java.net.http.HttpClient was added in Java 11.
The console module does not explicitly configure java.version, maven.compiler.source, or maven.compiler.target.
The console module's parent is org.apache.seata:seata-parent, which also does not define these properties.
org.apache.seata:seata-parent's parent is org.apache.seata:seata-build, which configures:
As a result, the console module inherits Java 1.8 compile target, but the source code uses java.net.http.HttpClient which requires Java 11+.
Ⅲ. Describe what you expected to happen
The console module should compile successfully with a Java version that supports java.net.http.HttpClient (Java 11+), without compilation errors in IDEA.
Ⅳ. How to reproduce it (as minimally and precisely as possible)
Open the Seata project in IntelliJ IDEA.
Navigate to the console module.
Observe the compilation error on java.net.http.HttpClient usage — it will be flagged as unavailable because the module is configured with Java 1.8 source/target level.
The error occurs because java.net.http.HttpClient is available starting from Java 11, but the inherited Maven compiler settings target Java 1.8.
Ⅴ. Anything else we need to know?
The fix is to add the following properties to console/pom.xml:
This overrides the inherited Java 1.8 setting from seata-build and aligns with the Spring Boot 4.0.6 / Spring Framework 7.0.7 baseline already used in the console module.
Check Ahead
I have searched the issues of this repository and believe that this is not a duplicate.
I am willing to try to fix this bug myself.
Ⅰ. Issue Description
The
consolemodule usesjava.net.http.HttpClient(introduced in Java 11), but the module is compiled with Java 8 compatibility settings inherited from the parent POM. This causes compilation errors when running in IDEA.Ⅱ. Describe what happened
When running the
consolemodule in IDEA, a compilation error related tojava.net.http.HttpClientoccurs:video
iShot_2026-07-24_13.09.05.mp4
Root Cause Analysis:
java.net.http.HttpClientwas added in Java 11.consolemodule does not explicitly configurejava.version,maven.compiler.source, ormaven.compiler.target.consolemodule's parent isorg.apache.seata:seata-parent, which also does not define these properties.org.apache.seata:seata-parent's parent isorg.apache.seata:seata-build, which configures:consolemodule inherits Java 1.8 compile target, but the source code usesjava.net.http.HttpClientwhich requires Java 11+.Ⅲ. Describe what you expected to happen
The
consolemodule should compile successfully with a Java version that supportsjava.net.http.HttpClient(Java 11+), without compilation errors in IDEA.Ⅳ. How to reproduce it (as minimally and precisely as possible)
consolemodule.java.net.http.HttpClientusage — it will be flagged as unavailable because the module is configured with Java 1.8 source/target level.java.net.http.HttpClientis available starting from Java 11, but the inherited Maven compiler settings target Java 1.8.Ⅴ. Anything else we need to know?
The fix is to add the following properties to
console/pom.xml:This overrides the inherited Java 1.8 setting from
seata-buildand aligns with the Spring Boot 4.0.6 / Spring Framework 7.0.7 baseline already used in the console module.Ⅵ. Environment
IntelliJ IDEA 2026.2.0.1