-
Notifications
You must be signed in to change notification settings - Fork 8
feat: Migrate codebase and dependencies to Java 17 #129
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
Conversation
…on to 2.15.4, okhttp to 4.12.0, wiremock to 2.27.2. Refactored `AttachmentsApiTest`. Resteasy changed order in the new version.
| <dependency> | ||
| <groupId>javax.annotation</groupId> | ||
| <artifactId>javax.annotation-api</artifactId> | ||
| <version>1.3.2</version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you can drop version here, it is defined in dependencyManagement
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we have to change the major version of sdk itsefl (1.26... --> 2.0.0)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, change the version and a couple more minor tweaks.
The purpose of this PR is to inform everyone that there will be a new major version (since all teams are actively working on updating services).
|
Okay, I take no comments as no objections. I'm closing this PR and releasing version 2.0.0. |
|
@dimitrystd, are we going to do the same branch for |
To All: I have no plans to merge this PR; it is only for visibility.
There is no way to keep
smartling-api-commonsfree of CVEs while continuing to support Java 8. I made only the necessary changes to migrate the code and dependencies to Java 17. This means that the SDK will exist in two versions, requiring each new development (endpoint) to be implemented twice.I'd like to encourage all teams to migrate their services from 1.x to the new 2.x (when it is released).