Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move to Java 17 as a language level #7688

Merged
merged 2 commits into from
Nov 24, 2022
Merged

Conversation

scholzj
Copy link
Member

@scholzj scholzj commented Nov 22, 2022

Type of change

  • Task

Description

The PR #7624 moved Strimzi operators to Java 17 as the runtime. This PR moves the Strimzi Operators to Java 17 as a language level as well.

The exception to this are the following modules - api, test, crd-generator and crd-annotations which stay on the Java 11 language level. The reason for that is that the api module is a published artifact which we expect users to use and we want it to be still usable in Java 11. The other 3 modules are dependnecies of the api module so they need to stay on Java 11 as well.

Java 17 also does a much more strict validation of the JavaDocs. When configured to raise warnings as errors, it requires Javadocs for all public classes, methods or fields. The PR #7664 already fixed Javadocs for most modules. But there are still hundreds of errors in the api, operator-common, cluster-operator and topic-operator modules. This PR for the time being disables the raising of warnings as errors for the time being. We should try to fix the Javadocs for operator-common, cluster-operator and topic-operator in the future. But I would suggest to keep this disabled for api permanently. The api classes are mostly getters and setters without any real functionality. Documenting all of them will not add much value but will be a lot of effort. In addition, the missing comments are also on the generated classes where we cannot add the comments easily but we want to have them in the Javadocs as well.

This PR also updates the Azure pipelines to use Java 17 and updates various Maven plugins to make them compatible with Java 17.

Checklist

  • Make sure all tests pass
  • Update documentation
  • Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
  • Update CHANGELOG.md

@scholzj scholzj added this to the 0.33.0 milestone Nov 22, 2022
@scholzj
Copy link
Member Author

scholzj commented Nov 23, 2022

/azp run regression

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@scholzj scholzj force-pushed the move-to-java-17-language-level branch from d12c68b to 4abc026 Compare November 24, 2022 00:20
@scholzj
Copy link
Member Author

scholzj commented Nov 24, 2022

/azp run regression

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@scholzj
Copy link
Member Author

scholzj commented Nov 24, 2022

/azp run kraft-regression

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@scholzj
Copy link
Member Author

scholzj commented Nov 24, 2022

/azp run helm-acceptance

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@scholzj scholzj marked this pull request as ready for review November 24, 2022 09:42
CHANGELOG.md Outdated Show resolved Hide resolved
@scholzj
Copy link
Member Author

scholzj commented Nov 24, 2022

/azp run feature-gates-regression

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Signed-off-by: Jakub Scholz <www@scholzj.com>
Signed-off-by: Jakub Scholz <www@scholzj.com>
@scholzj scholzj force-pushed the move-to-java-17-language-level branch from 4abc026 to af4b6dc Compare November 24, 2022 17:01
@scholzj scholzj merged commit 21ef5c5 into main Nov 24, 2022
@scholzj scholzj deleted the move-to-java-17-language-level branch November 24, 2022 18:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants