-
Notifications
You must be signed in to change notification settings - Fork 0
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
Build fails on JDK 22-ea #67
Comments
Thanks for reporting, @SethTisue . I’ll take a look… |
WIP on branch First off, I noticed that the community build |
Something is awry with Lombok code generation... The problem isn't due to the Running SBT under JDK 20, all is fine and Lombok generates the necessary builder method. I did wonder whether the SBT version upgrade from 1.8.3 to 1.9.7 might have had a bearing, but if so, this has been a problem since 1.9.0-RC1. Given the build is successful under JDK 20, I'm inclined to keep the hypothesis simple and blame either Lombok itself running within JDK 22 or something about the interaction between SBT and Lombok that doesn't play well with JDK 22... |
Rather than fight the unholy trinity of SBT, Lombok and JDK 22, having noticed that the class exhibiting the missing symbol was deprecated, I've avoided the issue by removing it a little earlier than I'd envisioned as of Git SHA e9c114f. |
@SethTisue I've fast-forwarded the I did however locally modify I'm not sure whether you manually edit the I have some general code cleanup to do engendered by this work, so I'll leave this ticket open for a while and won't do a release just yet. If there are further issues with the community build, let me know on this ticket... |
after scala/community-build@8ec83f1 americium is green at https://scala-ci.typesafe.com/job/scala-2.13.x-jdk22-integrate-community-build/10/consoleFull 👍 |
this came up over at scala/community-build#1698
the error log is at https://scala-ci.typesafe.com/job/scala-2.13.x-jdk22-integrate-community-build/5/artifact/logs/americium-build.log
obviously it's early to be worrying about JDK 22, but reporting regardless :-)
The text was updated successfully, but these errors were encountered: