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

Is there a plan to upgrade to Spring boot 3 & Spring 6? #1351

Closed
KeshavRathi opened this issue Dec 9, 2022 · 3 comments · Fixed by #1471
Closed

Is there a plan to upgrade to Spring boot 3 & Spring 6? #1351

KeshavRathi opened this issue Dec 9, 2022 · 3 comments · Fixed by #1471
Milestone

Comments

@KeshavRathi
Copy link

Is there a plan to upgrade to Spring boot 3 & Spring 6

Context

A project of our uses Riptide and we wanted to upgrade the Spring version in it but can't as Riptide still uses the previous version and has few deprecated classes.

@fatroom
Copy link
Member

fatroom commented Dec 9, 2022

We evaluating upgrade to spring boot 3, but no established timeline for a moment

@fatroom
Copy link
Member

fatroom commented Dec 16, 2022

At the moment there's no immediate plans to upgrade.
Some of our dependencies are not ready to be used with spring 6 (i.e. rest-driver) neither appropriate replacement (wiremock in unit test mode).

If you want to work on upgrade I would be happy to support with reviews and release of the new version.

@fatroom fatroom mentioned this issue Jan 16, 2023
6 tasks
@fatroom
Copy link
Member

fatroom commented Jan 16, 2023

Steps needs to be performed before migration to spring 6:

Open points:

  1. deprecate async Http (?) / find the way to work with reactive spring? maybe outside of the basic spring 6 migration
  2. evaluate interface based http clients and decide if can be supported?
  3. is migration guide required?

@fatroom fatroom added this to the 4.0.0 milestone Jan 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants