Caideyipi opened a new pull request, #18442: URL: https://github.com/apache/iotdb/pull/18442
## Description Cherry-pick `02f43e73f4705186210c2ec9d7e07bb16827b2a5` from `master` to `dev/1.3`. Original PR: #18431 This upgrades Eclipse Milo from 0.6.14 to 1.1.6, migrates the OPC UA server/client code to the Milo 1.x APIs, and carries over the security hardening and TCP None compatibility coverage from the original change. ### Draft blocker: Java baseline incompatibility `dev/1.3` compiles with `maven.compiler.release=8`, while the Milo 1.1.6 artifacts use Java 17 bytecode (class-file major version 61). Milo 1.1.6 types also use Java 17 classes such as `java.lang.Record`; for example, `org.eclipse.milo.opcua.stack.core.types.builtin.DateTime` extends `java.lang.Record`. The focused DataNode build therefore currently fails during compilation under the `dev/1.3` Java 8 target. Before this PR can be made ready, the branch needs a decision on whether to raise its Java baseline or use a Java 8-compatible upstream remediation. This draft intentionally keeps the cherry-pick close to the original change while that decision is pending. ### Verification - DataNode Spotless: passed; 0 files changed. - OPC UA example and integration-test Spotless: passed; 0 files changed. - DataNode Checkstyle: passed with 0 violations. - Focused OPC UA tests were requested but did not run because compilation stopped at the Java 8/17 incompatibility described above. <hr> This PR has: - [x] been self-reviewed. - [x] added or updated dependency version information. - [x] added or updated unit tests. - [x] added integration-test coverage. <hr> ##### Key changed/added classes - `OpcUaServerBuilder` - `OpcUaNameSpace` - `IoTDBOpcUaClient` - `ClientRunner` - `OpcUaTcpNoneCompatibilityTest` - OPC UA example client classes - `IoTDBPipeOPCUAIT` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
