Skip to content
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

Scala 3.5.0 a #299

Merged
merged 13 commits into from
Aug 27, 2024
17 changes: 16 additions & 1 deletion .github/workflows/build.yml
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ jobs:
runs-on: ubuntu-latest
strategy:
matrix:
scalaVersion: ['2.12.19', '2.13.14', '3.3.3', '3.4.3']
scalaVersion: ['2.12.19', '2.13.14', '3.4.3', '3.5.0']
javaTag: [
'graalvm-community-22.0.1',
'graalvm-community-21.0.2',
Expand Down Expand Up @@ -72,6 +72,21 @@ jobs:
dockerfile: 'alpine.Dockerfile'
baseImageTag: '17.0.10_7-jdk-alpine'
platforms: 'linux/amd64'
exclude:
# https://github.com/VirtusLab/scala-cli/issues/3130
- scalaVersion: '3.5.0'
javaTag: 'graalvm-community-22.0.1'
- scalaVersion: '3.5.0'
javaTag: 'graalvm-community-21.0.2'
- scalaVersion: '3.5.0'
javaTag: 'graalvm-ce-22.3.3-b1-java17'
# https://github.com/VirtusLab/scala-cli/issues/2758
# - scalaVersion: '3.5.0'
# javaTag: 'eclipse-temurin-alpine-22_36'
# - scalaVersion: '3.5.0'
# javaTag: 'eclipse-temurin-alpine-21.0.2_13'
# - scalaVersion: '3.5.0'
# javaTag: 'eclipse-temurin-alpine-17.0.10_7'
steps:
- uses: actions/checkout@v4
- name: Set up QEMU
Expand Down
8 changes: 5 additions & 3 deletions eclipse-temurin/Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -10,13 +10,13 @@

# Env variables
ARG SCALA_VERSION
ENV SCALA_VERSION ${SCALA_VERSION:-2.13.10}

Check warning on line 13 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-17.0.10_7)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 13 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-21.0.2_13)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 13 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-22_36)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 13 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-21.0.2_13)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 13 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-22_36)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 13 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-17.0.10_7)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 13 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-21.0.2_13)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 13 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-17.0.10_7)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 13 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-22_36)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 13 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-21.0.2_13)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 13 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-17.0.10_7)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 13 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-22_36)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
ARG SBT_VERSION
ENV SBT_VERSION ${SBT_VERSION:-1.6.2}

Check warning on line 15 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-17.0.10_7)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 15 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-21.0.2_13)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 15 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-22_36)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 15 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-21.0.2_13)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 15 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-22_36)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 15 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-17.0.10_7)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 15 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-21.0.2_13)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 15 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-17.0.10_7)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 15 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-22_36)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 15 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-21.0.2_13)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 15 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-17.0.10_7)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 15 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-22_36)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
ARG USER_ID
ENV USER_ID ${USER_ID:-1001}

Check warning on line 17 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-17.0.10_7)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 17 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-21.0.2_13)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 17 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-22_36)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 17 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-21.0.2_13)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 17 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-22_36)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 17 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-17.0.10_7)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 17 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-21.0.2_13)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 17 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-17.0.10_7)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 17 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-22_36)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 17 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-21.0.2_13)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 17 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-17.0.10_7)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 17 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-22_36)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
ARG GROUP_ID
ENV GROUP_ID ${GROUP_ID:-1001}

Check warning on line 19 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-17.0.10_7)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 19 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-21.0.2_13)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 19 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-22_36)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 19 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-21.0.2_13)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 19 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-22_36)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 19 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-17.0.10_7)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 19 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-21.0.2_13)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 19 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-17.0.10_7)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 19 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-22_36)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 19 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-21.0.2_13)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 19 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-17.0.10_7)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 19 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-22_36)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

# Install dependencies
# curl for downloading sbt and scala
Expand Down Expand Up @@ -44,11 +44,13 @@
chown -R root:root /usr/share/scala && \
chmod -R 755 /usr/share/scala && \
ln -s /usr/share/scala/bin/* /usr/local/bin && \
mkdir -p /test && \
case $SCALA_VERSION in \
"3"*) echo '@main def main = println(s"Scala library version ${dotty.tools.dotc.config.Properties.versionNumberString}")' > test.scala ;; \
*) echo "println(util.Properties.versionMsg)" > test.scala ;; \
"3"*) echo 'import java.io.FileInputStream;import java.util.jar.JarInputStream;val scala3LibJar = classOf[CanEqual[_, _]].getProtectionDomain.getCodeSource.getLocation.toURI.getPath;val manifest = new JarInputStream(new FileInputStream(scala3LibJar)).getManifest;val ver = manifest.getMainAttributes.getValue("Implementation-Version");@main def main = println(s"Scala version ${ver}")' > /test/test.scala ;; \
*) echo "println(util.Properties.versionMsg)" > /test/test.scala ;; \
esac && \
scala -nocompdaemon test.scala && rm test.scala
scala -nocompdaemon test/test.scala && \
rm -fr test

# Symlink java to have it available on sbtuser's PATH
RUN ln -s /opt/java/openjdk/bin/java /usr/local/bin/java
Expand Down Expand Up @@ -86,4 +88,4 @@
## -w /home/sbtuser
WORKDIR /root

CMD sbt

Check warning on line 91 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-17.0.10_7)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-21.0.2_13)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-jammy-22_36)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-21.0.2_13)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-22_36)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-jammy-17.0.10_7)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-21.0.2_13)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-17.0.10_7)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-jammy-22_36)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-21.0.2_13)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-17.0.10_7)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-jammy-22_36)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
4 changes: 2 additions & 2 deletions eclipse-temurin/alpine.Dockerfile
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Use a multi-stage build to reduce the size of the final image
ARG BASE_IMAGE_TAG
FROM eclipse-temurin:${BASE_IMAGE_TAG:-21.0.2_13-jdk-alpine} as builder

Check warning on line 3 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-alpine-17.0.10_7)

The 'as' keyword should match the case of the 'from' keyword

FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Check warning on line 3 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-alpine-21.0.2_13)

The 'as' keyword should match the case of the 'from' keyword

FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Check warning on line 3 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-alpine-22_36)

The 'as' keyword should match the case of the 'from' keyword

FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Check warning on line 3 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-alpine-22_36)

The 'as' keyword should match the case of the 'from' keyword

FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Check warning on line 3 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-alpine-21.0.2_13)

The 'as' keyword should match the case of the 'from' keyword

FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Check warning on line 3 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-alpine-17.0.10_7)

The 'as' keyword should match the case of the 'from' keyword

FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Check warning on line 3 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-alpine-17.0.10_7)

The 'as' keyword should match the case of the 'from' keyword

FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Check warning on line 3 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-alpine-22_36)

The 'as' keyword should match the case of the 'from' keyword

FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Check warning on line 3 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-alpine-21.0.2_13)

The 'as' keyword should match the case of the 'from' keyword

FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Check warning on line 3 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-alpine-17.0.10_7)

The 'as' keyword should match the case of the 'from' keyword

FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Check warning on line 3 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-alpine-21.0.2_13)

The 'as' keyword should match the case of the 'from' keyword

FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Check warning on line 3 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-alpine-22_36)

The 'as' keyword should match the case of the 'from' keyword

FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

ARG SCALA_VERSION=3.4.0
ARG SBT_VERSION=1.9.9
Expand All @@ -24,8 +24,8 @@
update-ca-certificates && \
scala -version && \
case $SCALA_VERSION in \
"3"*) echo '@main def main = println(s"Scala library version ${dotty.tools.dotc.config.Properties.versionNumberString}")' > test.scala ;; \
*) echo "println(util.Properties.versionMsg)" > test.scala ;; \
"3"*) echo 'import java.io.FileInputStream;import java.util.jar.JarInputStream;val scala3LibJar = classOf[CanEqual[_, _]].getProtectionDomain.getCodeSource.getLocation.toURI.getPath;val manifest = new JarInputStream(new FileInputStream(scala3LibJar)).getManifest;val ver = manifest.getMainAttributes.getValue("Implementation-Version");@main def main = println(s"Scala version ${ver}")' > test.scala ;; \
*) echo "println(util.Properties.versionMsg)" > test.scala ;; \
esac && \
scala -nocompdaemon test.scala && rm test.scala

Expand Down Expand Up @@ -88,4 +88,4 @@
## -w /home/sbtuser
WORKDIR /root

CMD sbt

Check warning on line 91 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-alpine-17.0.10_7)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-alpine-21.0.2_13)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, eclipse-temurin-alpine-22_36)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-alpine-22_36)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-alpine-21.0.2_13)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, eclipse-temurin-alpine-17.0.10_7)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-alpine-17.0.10_7)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-alpine-22_36)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, eclipse-temurin-alpine-21.0.2_13)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-alpine-17.0.10_7)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-alpine-21.0.2_13)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 91 in eclipse-temurin/alpine.Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.5.0, eclipse-temurin-alpine-22_36)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
2 changes: 1 addition & 1 deletion graalvm-ce/Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -10,14 +10,14 @@

# Env variables
ARG SCALA_VERSION
ENV SCALA_VERSION ${SCALA_VERSION:-2.13.10}

Check warning on line 13 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-ce-22.3.3-b1-java17)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 13 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-ce-22.3.3-b1-java17)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 13 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-ce-22.3.3-b1-java17)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
ARG SBT_VERSION
ENV SBT_VERSION ${SBT_VERSION:-1.6.2}

Check warning on line 15 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-ce-22.3.3-b1-java17)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 15 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-ce-22.3.3-b1-java17)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 15 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-ce-22.3.3-b1-java17)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
ENV JAVA_OPTS -XX:+UseG1GC

Check warning on line 16 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-ce-22.3.3-b1-java17)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 16 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-ce-22.3.3-b1-java17)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 16 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-ce-22.3.3-b1-java17)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
ARG USER_ID
ENV USER_ID ${USER_ID:-1001}

Check warning on line 18 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-ce-22.3.3-b1-java17)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 18 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-ce-22.3.3-b1-java17)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 18 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-ce-22.3.3-b1-java17)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
ARG GROUP_ID
ENV GROUP_ID ${GROUP_ID:-1001}

Check warning on line 20 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-ce-22.3.3-b1-java17)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 20 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-ce-22.3.3-b1-java17)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 20 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-ce-22.3.3-b1-java17)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

# Install sbt
RUN \
Expand All @@ -39,7 +39,7 @@
chmod -R 755 /usr/share/scala && \
ln -s /usr/share/scala/bin/* /usr/local/bin && \
case $SCALA_VERSION in \
"3"*) echo '@main def main = println(s"Scala library version ${dotty.tools.dotc.config.Properties.versionNumberString}")' > test.scala ;; \
"3"*) echo 'import java.io.FileInputStream;import java.util.jar.JarInputStream;val scala3LibJar = classOf[CanEqual[_, _]].getProtectionDomain.getCodeSource.getLocation.toURI.getPath;val manifest = new JarInputStream(new FileInputStream(scala3LibJar)).getManifest;val ver = manifest.getMainAttributes.getValue("Implementation-Version");@main def main = println(s"Scala version ${ver}")' > test.scala ;; \
*) echo "println(util.Properties.versionMsg)" > test.scala ;; \
esac && \
scala -nocompdaemon test.scala && rm test.scala
Expand Down Expand Up @@ -77,4 +77,4 @@
## -w /home/sbtuser
WORKDIR /root

CMD sbt

Check warning on line 80 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-ce-22.3.3-b1-java17)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 80 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-ce-22.3.3-b1-java17)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 80 in graalvm-ce/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-ce-22.3.3-b1-java17)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
2 changes: 1 addition & 1 deletion graalvm-community/Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -10,14 +10,14 @@

# Env variables
ARG SCALA_VERSION
ENV SCALA_VERSION ${SCALA_VERSION:-2.13.12}

Check warning on line 13 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-community-21.0.2)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 13 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-community-22.0.1)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 13 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-community-22.0.1)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 13 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-community-21.0.2)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 13 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-community-21.0.2)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 13 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-community-22.0.1)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
ARG SBT_VERSION
ENV SBT_VERSION ${SBT_VERSION:-1.9.7}

Check warning on line 15 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-community-21.0.2)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 15 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-community-22.0.1)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 15 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-community-22.0.1)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 15 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-community-21.0.2)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 15 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-community-21.0.2)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 15 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-community-22.0.1)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
ENV JAVA_OPTS -XX:+UseG1GC

Check warning on line 16 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-community-21.0.2)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 16 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-community-22.0.1)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 16 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-community-22.0.1)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 16 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-community-21.0.2)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 16 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-community-21.0.2)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 16 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-community-22.0.1)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
ARG USER_ID
ENV USER_ID ${USER_ID:-1001}

Check warning on line 18 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-community-21.0.2)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 18 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-community-22.0.1)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 18 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-community-22.0.1)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 18 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-community-21.0.2)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 18 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-community-21.0.2)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 18 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-community-22.0.1)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
ARG GROUP_ID
ENV GROUP_ID ${GROUP_ID:-1001}

Check warning on line 20 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-community-21.0.2)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 20 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-community-22.0.1)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 20 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-community-22.0.1)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 20 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-community-21.0.2)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 20 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-community-21.0.2)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 20 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-community-22.0.1)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

# Install sbt
RUN \
Expand All @@ -39,7 +39,7 @@
chmod -R 755 /usr/share/scala && \
ln -s /usr/share/scala/bin/* /usr/local/bin && \
case $SCALA_VERSION in \
"3"*) echo '@main def main = println(s"Scala library version ${dotty.tools.dotc.config.Properties.versionNumberString}")' > test.scala ;; \
"3"*) echo 'import java.io.FileInputStream;import java.util.jar.JarInputStream;val scala3LibJar = classOf[CanEqual[_, _]].getProtectionDomain.getCodeSource.getLocation.toURI.getPath;val manifest = new JarInputStream(new FileInputStream(scala3LibJar)).getManifest;val ver = manifest.getMainAttributes.getValue("Implementation-Version");@main def main = println(s"Scala version ${ver}")' > test.scala ;; \
*) echo "println(util.Properties.versionMsg)" > test.scala ;; \
esac && \
scala -nocompdaemon test.scala && rm test.scala
Expand Down Expand Up @@ -77,4 +77,4 @@
## -w /home/sbtuser
WORKDIR /root

CMD sbt

Check warning on line 80 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-community-21.0.2)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 80 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.12.19, graalvm-community-22.0.1)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 80 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-community-22.0.1)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 80 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (2.13.14, graalvm-community-21.0.2)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 80 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-community-21.0.2)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Check warning on line 80 in graalvm-community/Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.4.3, graalvm-community-22.0.1)

JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals

JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/