-
Notifications
You must be signed in to change notification settings - Fork 576
Update scala versions #304
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2,6 +2,6 @@ resolvers += Classpaths.sbtPluginReleases | |
| resolvers += Resolver.sonatypeRepo("snapshots") | ||
|
|
||
| addSbtPlugin("com.typesafe.sbt" % "sbt-site" % "1.4.1") | ||
| addSbtPlugin("org.scoverage" % "sbt-scoverage" % "1.9.1") | ||
| addSbtPlugin("org.scoverage" % "sbt-scoverage" % "1.9.3") | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. sbt-scoverage 2.0.0 is now out and upgrade seems to be smooth (from my experience with other projects)
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I tried that first but ran into all sorts of problems, so I changed the PR to be more conservative. My main goal here is using a recent Scala 3 version. I only update Scala 2.x versions until it became painful to go further (e.g. 2.12.16 and 2.13.8 both caused issues). |
||
| addSbtPlugin("pl.project13.scala" % "sbt-jmh" % "0.4.3") | ||
| addSbtPlugin("ch.epfl.scala" % "sbt-scalafix" % "0.9.31") | ||
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.
There is a merge conflict because a PR was merged that changed this to 3.0.2 - building with 3.0.2 is better imho because classes will work with Scala 3.0.x and 3.1.x. If you compile with 3.1.3, then the classes will not work with Scala 3.0.x runtime.
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.
Are you sure about that? I thought binary compatibility was finally solved by the Tasty mechanism.
The libraries published to Maven also don't specify anything beyond "_3" as the version suffix.
If there is really still a problem I don't mind building with 3.0.x for the moment, though.
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.
Have a read of https://issues.apache.org/jira/browse/LOG4J2-3524 and its link
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.
Ok, I see. That's unfortunate.
I will rework/close my PRs as soon as I find the time.