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

Upgrade to Java 17 #493

Closed
4 of 5 tasks
michael-simons opened this issue May 9, 2022 · 0 comments · Fixed by #717
Closed
4 of 5 tasks

Upgrade to Java 17 #493

michael-simons opened this issue May 9, 2022 · 0 comments · Fixed by #717
Labels

Comments

@michael-simons
Copy link
Owner

michael-simons commented May 9, 2022

This will happen with version 2.0 and includes:

  • Removing the Java 11 and Java 17 extra directories (compiling only for Java 17)
  • General improvements (text blocks, a couple of switch statements and the usual)
  • Upgrade to Graal 22.2
  • Add explicit tests for the module path (Turns out: I don't have too, stuff runs by default on mp, so 🤷 )
  • Test resources are patched into the main module, class graph finds them twice, tests fails (Duplicate resources found with Maven / Surefire patching test resources into the module path. classgraph/classgraph#704, unsure if this should be seen as maven / buildtool, module path or class graph issue, decided to move the affected resources into a separate (maven) module instead of using <useModulePath>false</useModulePath>)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant