-
Notifications
You must be signed in to change notification settings - Fork 1.1k
chore: add support for sbt-test
in the new build
#23748
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
base: main
Are you sure you want to change the base?
Conversation
…nstead of `semver-spec` (#23753) In some scenarios, specifically in cross compilation projects, sbt will complain that `scala-library:2.13.x` and `scala-library:3.x.y` might be imcompatible, as they are both declared `semver-spec`. See en example here: ```scala [error] (update) found version conflict(s) in library dependencies; some are suspected to be binary incompatible: [error] [error] * org.scala-lang:scala-library:3.8.0-RC1-bin-SNAPSHOT (semver-spec) is selected over 2.13.0 [error] +- org.scala-lang:scala3-library_3:3.8.0-RC1-bin-SNAPSHOT (depends on 3.8.0-RC1-bin-SNAPSHOT) [error] +- org.scala-lang.modules:scala-xml_2.13:1.2.0 (depends on 2.13.0) ``` In this PR, we change the version scheme of both `scala-library` and `scalajs-scalalib_2.13` to `always` so that the transition between the old stdlib structure and the new one stay invisible to the users. In the future, when we break binary compatibility (meaning Scala 4), we can revert this PR and have artifacts labeled with `semver-spec` as it will be exactly that scheme. --- The correctness was validated in #23748 locally. [skip ci]
0341c3f
to
9a24c0a
Compare
e717cd2
to
1a0d946
Compare
- name: Generate documentation for example project using dotty-sbt | ||
run: ./project/scripts/sbt "sbt-test/scripted sbt-dotty/scaladoc" | ||
|
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.
We will be running these alongside all the other scripted tests anyways, no need to run them twice.
1a0d946
to
c83f49b
Compare
c83f49b
to
6622343
Compare
6622343
to
3d55eda
Compare
run: | | ||
./project/scripts/buildScalaBinary | ||
./project/scripts/sbt ";scala3-bootstrapped/compile ;sbt-test/scripted scala2-compat/* ;scala3-compiler-bootstrapped/scala3CompilerCoursierTest:test" | ||
./project/scripts/sbt ";scala3-bootstrapped/compile ;scala3-bootstrapped/publishLocal ;scala3-compiler-bootstrapped/scala3CompilerCoursierTest:test" |
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.
sbt-test/scripted
had the side effect of publishing the artifacts locally, which is needed by the following scripts. This will be made very clear when removing these tests.
This PR configures the scripted tests (
sbt-test
) to be run using the new stdlib.This PR should fail at the moment as we do not have thescaladoc
artifacts yet in the build.