-
Notifications
You must be signed in to change notification settings - Fork 23
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
Miscellaneous Scala cleanup #1006
Conversation
Important Auto Review SkippedDraft detected. Please check the settings in the CodeRabbit UI or the To trigger a single review, invoke the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
93897bc
to
0adb19a
Compare
bd80088
to
6974d78
Compare
#1006 is failing because the Scala Maven plugin is trying to download the sources for the compiler bridge, but can't do so outside of a Nix FOD. This PR adds the bridge to the manually-downloaded Maven artifacts (as we did in runtimeverification/k#4055)
Will need the changes to Maven usage from: runtimeverification/k#4108 |
This PR makes a couple quick changes analogous to runtimeverification/k#4055:
scala-maven-plugin
to its latest version<release>
inmaven-compiler-plugin
inherited from the parent POM, rather than manually setting-source
and-target
forjavac
-Werror
case _ => ???
. This is poor style and an abuse of???
IMO, but it's already pervasive throughout our codebase.