#22037 closed defect (fixed)
"Projekt Java-EarlyAccess-Update-JDK" fails downloading Java with 404
Reported by: | mdk | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | |
Keywords: | java19 | Cc: |
Description
The Jenkins Job "Projekt Java-EarlyAccess-Update-JDK" fails with 404 on downloading
https://download.java.net/java/early_access/jdk19/12/GPL/openjdk-19-ea+12_linux-x64_bin.tar.gz
Attachments (0)
Change History (12)
comment:1 by , 3 years ago
comment:2 by , 3 years ago
Looking at the download page, the URL should be https://download.java.net/java/early_access/jdk19/19/GPL/openjdk-19-ea+19_linux-x64_bin.tar.gz
.
This appears to be a problem with the script we use ( https://github.com/sormuras/bach/blob/master/install-jdk.sh -- we download this from https://raw.githubusercontent.com/sormuras/bach/master/install-jdk.sh ).
Looking at the tickets, bach/250, it looks like the master
branch is intended to be deleted soon -- they also changed their default branch to main
(like many other projects).
Furthermore, it looks like that script is no longer supported (see bach/248). It has been removed from their main
branch.
So we should either (a) fork the script and update it ourselves, (b) switch to a different method of getting Java builds (in bach/250, jabba and sdkman were mentioned).
Of the two alternatives to the script, it looks like sdkman
is better -- I'm not seeing any Java 19 releases from jabba remote-ls
anyway.
Right now, I'm not particularly enamoured with sdkman
either -- it isn't very script friendly. It would be doable, but unwise (IMO) to attempt to script it.
Examples with sdkman
:
Java 18 GA
$ sdk install java 18-open
Java 19 EA
$ sdk install java $(sdk list java | awk -F'|' '/19/ && /open/ {print $6}' | head -n1) Downloading: java 19.ea.19-open In progress... Repackaging Java 19.ea.19-open... Done repackaging... Installing: java 19.ea.19-open Done installing! Do you want java 19.ea.19-open to be set as default? (Y/n):
Interactive question! But this can be fixed with echo "sdkman_auto_answer=true" > ~/.sdkman/etc/config
.
comment:3 by , 3 years ago
I've taken a look at the script we use.
We pretty much have to change a few lines in https://github.com/sormuras/bach/blob/releases/11/install-jdk.properties:
-
install-jdk.properties
2 2 # 3 3 # JDK 19 4 4 # 5 19-linux-aarch64=https://download.java.net/java/early_access/jdk19/ 12/GPL/openjdk-19-ea+12_linux-aarch64_bin.tar.gz6 19-linux-x64=https://download.java.net/java/early_access/jdk19/ 12/GPL/openjdk-19-ea+12_linux-x64_bin.tar.gz5 19-linux-aarch64=https://download.java.net/java/early_access/jdk19/20/GPL/openjdk-19-ea+20_linux-aarch64_bin.tar.gz 6 19-linux-x64=https://download.java.net/java/early_access/jdk19/20/GPL/openjdk-19-ea+20_linux-x64_bin.tar.gz 7 7 19-linux-x64-musl=https://download.java.net/java/early_access/alpine/5/binaries/openjdk-19-ea+5_linux-x64-musl_bin.tar.gz 8 19-macos-aarch64=https://download.java.net/java/early_access/jdk19/ 12/GPL/openjdk-19-ea+12_macos-aarch64_bin.tar.gz9 19-macos-x64=https://download.java.net/java/early_access/jdk19/ 12/GPL/openjdk-19-ea+12_macos-x64_bin.tar.gz10 19-windows-x64=https://download.java.net/java/early_access/jdk19/ 12/GPL/openjdk-19-ea+12_windows-x64_bin.zip8 19-macos-aarch64=https://download.java.net/java/early_access/jdk19/20/GPL/openjdk-19-ea+20_macos-aarch64_bin.tar.gz 9 19-macos-x64=https://download.java.net/java/early_access/jdk19/20/GPL/openjdk-19-ea+20_macos-x64_bin.tar.gz 10 19-windows-x64=https://download.java.net/java/early_access/jdk19/20/GPL/openjdk-19-ea+20_windows-x64_bin.zip 11 11 12 12 # 13 13 # JDK 18
We'd also have to change the download link in https://github.com/sormuras/bach/blob/releases/11/install-jdk.sh for the properties file.
comment:4 by , 3 years ago
Keywords: | java19 added |
---|
comment:7 by , 3 years ago
Replying to stoecker:
Simply copy the stuff to our SVN and relink to it?
Definitely an option. I'm OK with that, with the caveat that we're going to have to maintain it, and I had to (effectively) hand-edit the install-jdk.properties
file.
It does look like there might be an automated way to update the properties file.
It looks like we'll want, at minimum:
comment:8 by , 3 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
It looks like @stoecker fixed this in https://josm.openstreetmap.de/jenkins/job/Java-EarlyAccess-Update-JDK/1356/.
comment:9 by , 3 years ago
The same problem occurs again since 20.7.2022 while downloading https://download.java.net/java/early_access/jdk19/20/GPL/openjdk-19-ea+20_linux-x64_bin.tar.gz
comment:10 by , 3 years ago
Yep. Rather unfortunately, both stoecker and Don-vip aren't very active right now (life happens), and only someone with server admin access can fix it, at this time. I think.
I believe stoecker copied the files I linked into the Jenkins instance, but it doesn't look like we are running the ShowJdkBuilds.java
script automatically.
TBH, we should either put it in svn somewhere (either source:josm/trunk/scripts or someplace in source:osm/applications/editors/josm) or have it set up to run automatically when Java-EarlyAccess-Update-JDK fails.
comment:11 by , 3 years ago
If you assign or CC me in tickets I'll see and react.
I updated the install-jdk.properties for Java 19 and Java 20 EA 10.
comment:12 by , 19 months ago
Ok. I disabled Early access and switched Java 11 to Java 17 for JOSM and Plugins.
Remains to add java 20 and 21 and enabled these as well.
Ooops. Wrong ticket. See #23218
And also "Java-EarlyAccess-JOSM" for Java19 is failing with