-
Notifications
You must be signed in to change notification settings - Fork 48
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
Using sbt-typelevel 0.7.3 by itself raises java.lang.NoSuchMethodError #750
Comments
and this leads to the problem https://github.com/armanbilge/scala-native-config-brew/blob/main/build.sbt#L74C18-L74C76 (A I think the only way would be to update https://github.com/armanbilge/scala-native-config-brew (by merging a bunch or open PRs ans making a release) |
v0.7.3 is backwards-compatible with v0.7.0. sbt should be evicting v0.7.0 automatically in favor of v0.7.3. But I don't see that happening in the evictions ...
I'm not sure what's happening, but at the moment this seems like an sbt bug. |
@takapi327 As a workaround, try adding an explicit dependency: addSbtPlugin("org.typelevel" % "sbt-typelevel-github-actions" % "0.7.3") I think this will make eviction work properly.
|
@armanbilge Thank you! |
Hi 👋
First of all, I would like to thank you for your constant maintenance.
Oddly enough, using the latest version that was recently released seems to cause a java.lang.NoSuchMethodError.
Specifically, when I run Test with sbt-typelevel 0.7.3 by itself, I get java.lang.NoSuchMethodError.
I had no problems when using 0.7.2.
Environment
Here is the environment where I encountered this error.
Error
This is the actual error that occurred.
You can also refer to the actual error here.
https://github.com/takapi327/ldbc/actions/runs/11092834144/job/30818362773?pr=288
I looked at the difference from 0.7.2 to 0.7.3 and it looks like only the name of the
appendToStepSummary
method that is causing the error has changed only slightly.Workaround
Looking at the updates of other Typelevel projects, sbt-typelevel-site was also used in conjunction. I did not see the same error in that project.
When I tried using sbt-typelevel-site together, the error did not occur.
Is there anything we missed or something that needs to be addressed in the new version?
Thank you.
The text was updated successfully, but these errors were encountered: