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.

Sign up for GitHub

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

Jump to bottom

Switch to JDK17 #1391

Closed
fatroom opened this issue Jan 31, 2023 · 1 comment · Fixed by #1395
Closed

Switch to JDK17 #1391

fatroom opened this issue Jan 31, 2023 · 1 comment · Fixed by #1395
Assignees
@fatroom
Labels
Feature
Milestone
4.0.0

Comments

@fatroom
Copy link
Member

fatroom commented Jan 31, 2023

Context

The more and more dependencies switching to JDK17.
The next riptide major release will be based on the Spring 6, which bring JDK17 as dependency.
There's no benefit to use intermediate JDK version for minor release (i.e. 11) so upgrade should go directly to 17.

Possible Implementation

To untangle javax to jakarta move, only build process and JDK should be upgraded first.
@fatroom fatroom added this to the 4.0.0 milestone Jan 31, 2023
@fatroom fatroom mentioned this issue Jan 31, 2023
Closed
@fatroom
Copy link
Member Author

fatroom commented Jan 31, 2023

Possible implementations are #1386 or #1377
Initial author seems absconded them, so either finish one of this PR to implement this issue, or create new PR

@fatroom fatroom mentioned this issue Jan 31, 2023
Merged
6 tasks
@fatroom fatroom self-assigned this Feb 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fatroom fatroom

Labels
Feature
Projects
None yet
Milestone
4.0.0
Development

Successfully merging a pull request may close this issue.

Switched JDK build to 17 zalando/riptide
1 participant
@fatroom