feat: Move Access Operator to Java 17 - Githubissues

strimzi / kafka-access-operator

Operator for sharing access to Strimzi clusters across namespaces

Apache License 2.0

17 stars 15 forks source link

feat: Move Access Operator to Java 17 #22

Closed mabulgu closed 1 year ago

mabulgu commented 1 year ago

Updates Java 11 to Java 17 in the following places:

Dockerfile (Runtime)
Language level (Build time)
CI pipeline
Dev. guide docs.

Verification:

All unit tests are passing. (There are no integration tests yet)
Tested by running the operator locally and the resources on minikube.
Tested by running the operator instance on minikube.

[strimzi@strimzi-access-operator-cc56486fc-6wsg2 strimzi]$ java --version
openjdk 17.0.6 2023-01-17 LTS
OpenJDK Runtime Environment (Red_Hat-17.0.6.0.10-3.el8_7) (build 17.0.6+10-LTS)
OpenJDK 64-Bit Server VM (Red_Hat-17.0.6.0.10-3.el8_7) (build 17.0.6+10-LTS, mixed mode, sharing)

Some notes:

Changed the docs plugin failOnWarnings config on pom.xml from true to false. We should either write comments on top of the methods or dont fail on warnings. This prevented me to do the build after Java 17 update.
I directly changed the versions from 11 to 17 in the pipelines. There is a test matrix included and was not sure to keep 11 as we can discuss which version's support to keep, which to include in the matrix etc.