-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Fix NoClassDefFoundError when using old zinc version [ci: last-only]
#10964
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
Fix NoClassDefFoundError when using old zinc version [ci: last-only]
#10964
Conversation
|
(labeled "internal" since the problem it addresses never appeared in a release) |
NoClassDefFoundError when using old zinc versionNoClassDefFoundError when using old zinc version [ci: last-only]
|
Is there some way we can prevent this from recurring in the future? ("this" = accidentally depending on some too-new API) |
Maybe we can add exactly one build to scala community builds with an old sbt version? So every other builds in community builds run with latest sbt version but the one build does not. |
|
Thank you! |
94471e3 to
6507958
Compare
SethTisue
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll give the question of avoiding recurrence some thought in the new year.
|
This doesn't seem to fix the problem in the Scala Native repo, I still get this is from a clean checkout of scala-native with (on JDK 17) |
|
Oh, I bet it's because |
Thanks for the observation! Making another PR right now. |
|
I've just submitted #10966 |
|
I've verified that #10966 fixes the problem as originally reported in the Scala Native repo. |
c.c. #10905 (comment)
We explicitly catch the exception, as in
scala/src/sbt-bridge/scala/tools/xsbt/CompilerBridge.scala
Lines 158 to 160 in 1f34012
@SethTisue