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

Support Spring Framework 6 #5018

Open
NMAP97 opened this issue Oct 3, 2024 · 1 comment
Open

Support Spring Framework 6 #5018

NMAP97 opened this issue Oct 3, 2024 · 1 comment
Labels
backlog breaking change Any change which may break existing configurations and deployments maintenance Issues to help maintain the project, such as improving builds, testing, etc.
Milestone

Comments

@NMAP97
Copy link

NMAP97 commented Oct 3, 2024

Is your feature request related to a problem? Please describe.
Spring Framework v5.3.39 reached end of life. It would be better to upgrade to latest Spring Framework v6.1.
https://spring.io/blog/2024/03/01/support-timeline-announcement-for-spring-framework-6-0-x-and-5-3-x

Describe the solution you'd like
Upgrade Spring v5.3.39 to v6.1
https://github.com/spring-projects/spring-framework/wiki/Upgrading-to-Spring-Framework-6.x

Please let me know the current plan(if any) on upgrading to Spring Framework 6 and the future plans of the Spring Framework in data prepper project.

@dlvenable
Copy link
Member

@NMAP97 , This is a good point. One blocking issue is that Spring Framework 6.0 requires Java 17 and above. Currently, Data Prepper requires Java 11 as a minimum.

https://docs.spring.io/spring-framework/reference/overview.html

We have #3192 open to support Java 17 or 21 as a minimum starting in Data Prepper 3.0. So we won't be able to make this update until then.

For my understand, is there a particular reason you raised this issue? Is this blocking your usage of Data Prepper or were you interested in making changes to support this?

@dlvenable dlvenable added breaking change Any change which may break existing configurations and deployments maintenance Issues to help maintain the project, such as improving builds, testing, etc. labels Oct 3, 2024
@oeyh oeyh removed the untriaged label Oct 8, 2024
@dlvenable dlvenable added this to the v3.0 milestone Oct 8, 2024
@oeyh oeyh added the backlog label Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog breaking change Any change which may break existing configurations and deployments maintenance Issues to help maintain the project, such as improving builds, testing, etc.
Projects
Development

No branches or pull requests

3 participants