java feature "mavenVersion" latest is still using 3.9.9 and results in a corrupt archive error

[artis3n]

Trying to install the java feature results in an error unless you pin mavenVersion to the recently released 3.9.10 from June 1. 3.9.9 results in a corrupt archive error, and the default "latest" version if you don't specify mavenVersion still uses 3.9.9, so the feature fails to install in its default configuration. This has been going on for the last few days, I'm assuming since 6/1 when the newest Maven version was released.

{
	"name": "Debian",
	"image": "mcr.microsoft.com/devcontainers/base:bookworm",
	"features": {
            "ghcr.io/devcontainers/features/java:1": {
                "version": "24",
                "jdkDistro": "tem",
                "installMaven": true,
                "mavenVersion": "3.9.10"
            }
}

Works, but

{
	"name": "Debian",
	"image": "mcr.microsoft.com/devcontainers/base:bookworm",
	"features": {
            "ghcr.io/devcontainers/features/java:1": {
                "version": "24",
                "jdkDistro": "tem",
                "installMaven": true
            }
}

fails -

Pinning to Maven 3.9.8 works, so there's just an issue with 3.9.9, and it's an issue for this feature because it still uses 3.9.9 as the default "latest" version.

[Kaniska244]

Hello @artis3n ,

Thank you for reporting this issue. This issue seems to have been originated from PR when the CDN url was changed initially at sdkman. Then after that, last week new maven version 3.9.10 released by ASF project & they also did a clean-up such that, in the new CDN url used by sdkman has only the latest version of maven, ref .
However, the sdkman default version is still pointing to 3.9.9 which isn't available anymore in the CDN url currently used by sdkman. The folowing issues are created with sdkman already for the same. We at devcontainers side will check further if there can be a temporary workaround for this.

Open issues with sdkman repo:
sdkman/sdkman-cli#1458
sdkman/sdkman-db-migrations#730

[Kaniska244]

Only maven 3.9.9 is causing the problem & also the problem is that its the default version as pinned for the latest version in sdkman.
For 3.9.9 and 3.9.10 versions, sdkman is downloading the package from the new CDN url from ASF as can be seen below , please see the location value below. And this CDN url only contains the latest version i.e. 3.9.10.

root ➜ /usr/local/sdkman/tmp $ cat maven-3.9.10.headers.tmp
HTTP/1.1 302 Found
Server: nginx/1.19.10
Date: Thu, 12 Jun 2025 12:59:59 GMT
Content-Length: 0
Connection: keep-alive
X-Sdkman-ArchiveType: zip
location: https://dlcdn.apache.org/maven/maven-3/3.9.10/binaries/apache-maven-3.9.10-bin.zip

HTTP/2 200 
server: Apache
last-modified: Sun, 01 Jun 2025 18:55:10 GMT
etag: "893ae7-636872fc545ce"
access-control-allow-origin: *
content-type: application/zip
via: 1.1 varnish, 1.1 varnish
accept-ranges: bytes
date: Thu, 12 Jun 2025 13:07:53 GMT
age: 1827
x-served-by: cache-hel1410024-HEL, cache-sin-wsss1830097-SIN
x-cache: HIT, HIT
x-cache-hits: 22, 1
x-timer: S1749733674.693184,VS0,VE15
content-length: 8993511

root ➜ /usr/local/sdkman/tmp $ cat maven-3.9.9.headers.tmp
HTTP/1.1 302 Found
Server: nginx/1.19.10
Date: Thu, 12 Jun 2025 12:57:59 GMT
Content-Length: 0
Connection: keep-alive
X-Sdkman-ArchiveType: zip
location: https://dlcdn.apache.org/maven/maven-3/3.9.9/binaries/apache-maven-3.9.9-bin.zip

HTTP/2 404 
server: Apache
content-type: text/html; charset=iso-8859-1
via: 1.1 varnish, 1.1 varnish
accept-ranges: bytes
age: 190
date: Thu, 12 Jun 2025 13:05:53 GMT
x-served-by: cache-hel1410033-HEL, cache-sin-wsss1830097-SIN
x-cache: HIT, HIT
x-cache-hits: 8, 0
x-timer: S1749733554.952662,VS0,VE1
content-length: 196

root ➜ /usr/local/sdkman/tmp $ 

Whereas for the maven versions < 3.9.9, sdkman is still referring to the older apache maven repo where all versions are available including 3.9.9. It can be seen below, please see the location value. So they can still be installed with sdkman.

root ➜ /usr/local/sdkman/tmp $ cat maven-3.9.8.headers.tmp
HTTP/1.1 302 Found
Server: nginx/1.19.10
Date: Thu, 12 Jun 2025 12:58:11 GMT
Content-Length: 0
Connection: keep-alive
X-Sdkman-ArchiveType: zip
location: https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.8/apache-maven-3.9.8-bin.zip

HTTP/2 200 
etag: "0f007c1cc9ae9faa363f9cbcc70bfe52"
content-type: application/zip
last-modified: Thu, 13 Jun 2024 08:24:54 GMT
x-checksum-md5: 0f007c1cc9ae9faa363f9cbcc70bfe52
x-checksum-sha1: b147144def2882179e9418c8cda7c66f792adf1e
via: 1.1 varnish, 1.1 varnish
accept-ranges: bytes
age: 442975
date: Thu, 12 Jun 2025 13:06:06 GMT
x-served-by: cache-iad-kjyo7100125-IAD, cache-sin-wsss1830069-SIN
x-cache: HIT, HIT
x-cache-hits: 105134, 0
x-timer: S1749733566.030740,VS0,VE1
content-length: 9194897

root ➜ /usr/local/sdkman/tmp $ 
root ➜ /usr/local/sdkman/tmp $ cat maven-3.9.6.headers.tmp
HTTP/1.1 302 Found
Server: nginx/1.19.10
Date: Thu, 12 Jun 2025 13:11:38 GMT
Content-Length: 0
Connection: keep-alive
X-Sdkman-ArchiveType: zip
location: https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.6/apache-maven-3.9.6-bin.zip

HTTP/2 200 
etag: "3830cb789214ffb19d0c72a9f77812a6"
content-type: application/zip
last-modified: Tue, 28 Nov 2023 10:03:30 GMT
x-checksum-md5: 3830cb789214ffb19d0c72a9f77812a6
x-checksum-sha1: fc5c01a07e4a2ddf84af0dfadf382e6f7993462d
via: 1.1 varnish, 1.1 varnish
accept-ranges: bytes
date: Thu, 12 Jun 2025 13:19:32 GMT
age: 3832508
x-served-by: cache-iad-kcgs7200027-IAD, cache-sin-wsss1830069-SIN
x-cache: HIT, HIT
x-cache-hits: 82349, 1
x-timer: S1749734373.662483,VS0,VE20
content-length: 9513253

root ➜ /usr/local/sdkman/tmp $ 

[MiellyEllen]

I am an author of Several LinkedIn Learning Java courses. 2 courses use ghcr.io/devcontainers/features/java:1 in each branch. Each course contains at least 30 branches to walk through various coding examples.
On June 13 a learner pointed out this problem to me -- making it impossible to continue the courses. I have no idea how long this problem existed before then.
I depend on these courses as a stream of royalty revenue. Before I spend time modifying 60+ branches with the workaround, I was wondering how soon will this fix would be published.
Spring Data 3! I have made this course free for you.

[messeant]

Hello,

for my issue #1392, it's ok with add "mavenVersion": "3.9.10".

But when I am creating a devcontainer in a new project with

in vscode, "mavenVersion": "3.9.10". is not add in devcontainer.json.

It's a problem for the new project.