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

JDK 21 #679

Open
mjmk3 opened this issue Jan 18, 2024 · 4 comments
Open

JDK 21 #679

mjmk3 opened this issue Jan 18, 2024 · 4 comments

Comments

@mjmk3
Copy link

mjmk3 commented Jan 18, 2024

Hope you solve the problem with JDK 21 compatibility because it's not working till now has a lot of issues and bugs

@Venorcis
Copy link

Venorcis commented Feb 9, 2024

We're mainly seeing warnings because of the deprecation of java.net.URL constructors.

@mjmk3 did you encounter more specific problems?

@lukasj
Copy link
Member

lukasj commented Feb 9, 2024

Hope you solve the problem with JDK 21 compatibility because it's not working till now has a lot of issues and bugs

I have no idea what are you talking about. Do you see anything specific?

@Venorcis
Copy link

@lukasj is there a plan to refactor out the usage of deprecated URL constructors?

@lukasj
Copy link
Member

lukasj commented Feb 12, 2024

@lukasj is there a plan to refactor out the usage of deprecated URL constructors?

removing deprecated (not-only JDK) APIs is an on-going incremental process (see ie this PR), so it will happen at some point. Given URL constructors are not deprecated for removal it may take some time to get rid of them as removing APIs deprecated for removal are of higher priority (ie Object.finalize, SecurityManager). Feel free to submit a PR should there be a need to have this done sooner. Thanks.

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

No branches or pull requests

3 participants