Repository navigation
Using GA, got - Error: The string '18.0.1.1' is not valid SemVer notation for a Java version. #25
Description
Run oracle-actions/setup-java@v1
with:
website: jdk.java.net
release: GA
version: latest
install: true
Run JAVA=$JAVA_HOME_17_X64/bin/java
JAVA=$JAVA_HOME_17_X64/bin/java
DOWNLOAD=$GITHUB_ACTION_PATH/src/Download.java
if [ ! -z "" ]; then
$JAVA $DOWNLOAD
else
$JAVA $DOWNLOAD jdk.java.net GA latest
fi
shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
Archive openjdk-18.0.1.1_linux-x64_bin.tar.gz in file:///home/runner/.oracle-actions/setup-java/3eac1378/
Run actions/setup-java@v3
with:
java-version: 18.0.1.1
distribution: jdkfile
jdkFile: /home/runner/.oracle-actions/setup-java/3eac1378/openjdk-18.0.1.1_linux-x64_bin.tar.gz
java-package: jdk
architecture: x64
check-latest: false
server-id: github
server-username: GITHUB_ACTOR
server-password: GITHUB_TOKEN
overwrite-settings: true
job-status: success
Error: The string '18.0.1.1' is not valid SemVer notation for a Java version. Please check README file for code snippets and more detailed information
The build log is at: https://github.com/ebean-orm/ebean/runs/6267071973?check_suite_focus=true
Activity
sormuras commentedon May 3, 2022
Thanks for reporting this issue, Rob.
The documentation of actions/setup-java says:
I guess, "a whole Java version" of
18.0.1.1is not (yet) supported byactions/setup-java@3, or that the underlying semver parser has an issue.There are some temporary mitigation paths
oracle-actions/setup-javacan take:x.y.zas the version toactions/setup-java@3. Here, omit the trailing.1from18.0.1.1:18.0.1actions/setup-java@2and test whether18.0.1.1are supported.Truncate parsed version to `X.Y.Z`
sormuras commentedon May 3, 2022
Also errors for
oracle.com, when using specific archived version18.0.1.1. Using the defaultlatestas version works, as its version resolves to only the feature number18.Truncate parsed version to `X.Y.Z` (#26)
Include interim of `0` when update is present
sormuras commentedon May 3, 2022
Rob, please restart the failed workflow run(s). They should work now.
rbygrave commentedon May 3, 2022
Thanks. Yes, re-run and all good. Awesome, thanks !!