-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Implement Scala CLI as the scala
runner command
#20098
Labels
area:ci
Issues tied with CI/CD workflows
area:runner
Issues tied to the scala runner command.
itype:enhancement
Comments
10 tasks
the strategy of downloading the launcher looks looks slightly problematic for script files compiled with a higher tasty version than scala-cli itself (e.g. a new minor release): echo 'println(23)' >> local/foo.sc
scala-cli --cli-default-scala-version 3.5.0-RC1-bin-SNAPSHOT \
-r file://dist/target/pack/maven2 \
local/foo.sc \
--server=false
Scala CLI (v1.3.0) cannot post process TASTY files from Scala 3.5.0-RC1-bin-SNAPSHOT.
This is not a fatal error since post processing only cleans up source paths in TASTY file.
It should not affect your application.
You may be getting this warning because you are using a newer version of Scala than the one supported by Scala CLI (v1.3.0).
Make sure your Scala CLI is up-to-date.
You may need to wait for 3.5.0-RC1-bin-SNAPSHOT support in a future version of Scala CLI.
23 however it still executes this simple script, as the error says, its only a problem "cleaning up" the source paths. |
This was referenced May 2, 2024
This was referenced May 10, 2024
hamzaremmal
added a commit
that referenced
this issue
Jun 11, 2024
fixes #20098 Proposed changes to zip/targz archive: - in the `/bin` directory store an extra launcher for Scala CLI (either JAR, or native per platform). - `/bin/scala[.bat]` is modified to invoke Scala CLI stored in `/bin` - new `/maven2` directory, which stores all the Jars and POM files necessary (in maven repo style) for scala-cli to invoke scala compiler offline (using the `-r` launcher option). - CHOICE: either replace jar files in `/lib` by aliases to the corresponding jar in `/maven2`, OR delete `/lib` and update references from scripts. (Looks like symlinks are not portable, so probably we should encode the classpath in a file, or adjust slightly how we build the toolchain) - add platform specific suffixes to artefacts: - e.g. `scala-3.5.0-x86_64-pc-linux.tar.gz` (for the artefact that bundles the x64 linux launcher) --------- Co-authored-by: Hamza REMMAL <[email protected]>
WojciechMazur
pushed a commit
to WojciechMazur/dotty
that referenced
this issue
Jun 20, 2024
fixes scala#20098 Proposed changes to zip/targz archive: - in the `/bin` directory store an extra launcher for Scala CLI (either JAR, or native per platform). - `/bin/scala[.bat]` is modified to invoke Scala CLI stored in `/bin` - new `/maven2` directory, which stores all the Jars and POM files necessary (in maven repo style) for scala-cli to invoke scala compiler offline (using the `-r` launcher option). - CHOICE: either replace jar files in `/lib` by aliases to the corresponding jar in `/maven2`, OR delete `/lib` and update references from scripts. (Looks like symlinks are not portable, so probably we should encode the classpath in a file, or adjust slightly how we build the toolchain) - add platform specific suffixes to artefacts: - e.g. `scala-3.5.0-x86_64-pc-linux.tar.gz` (for the artefact that bundles the x64 linux launcher) --------- Co-authored-by: Hamza REMMAL <[email protected]>
WojciechMazur
pushed a commit
to WojciechMazur/dotty
that referenced
this issue
Jun 20, 2024
fixes scala#20098 Proposed changes to zip/targz archive: - in the `/bin` directory store an extra launcher for Scala CLI (either JAR, or native per platform). - `/bin/scala[.bat]` is modified to invoke Scala CLI stored in `/bin` - new `/maven2` directory, which stores all the Jars and POM files necessary (in maven repo style) for scala-cli to invoke scala compiler offline (using the `-r` launcher option). - CHOICE: either replace jar files in `/lib` by aliases to the corresponding jar in `/maven2`, OR delete `/lib` and update references from scripts. (Looks like symlinks are not portable, so probably we should encode the classpath in a file, or adjust slightly how we build the toolchain) - add platform specific suffixes to artefacts: - e.g. `scala-3.5.0-x86_64-pc-linux.tar.gz` (for the artefact that bundles the x64 linux launcher) --------- Co-authored-by: Hamza REMMAL <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area:ci
Issues tied with CI/CD workflows
area:runner
Issues tied to the scala runner command.
itype:enhancement
Corresponding Scala CLI issue
scala
runner command VirtusLab/scala-cli#2838Relevant docs
Requirements
scala
runner tests against the Scala CLI launcher on thescala/scala3
CIscala
runner in official Scala 3 distributionsThe text was updated successfully, but these errors were encountered: