You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by sl...@apache.org on 2026/08/04 13:18:03 UTC
(maven) branch maven-4.0.x updated (c37d45b2c6 -> 7f736da7ac)
This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a change to branch maven-4.0.x
in repository https://gitbox.apache.org/repos/asf/maven.git
from c37d45b2c6 Bump actions/setup-java from 5.6.0 to 5.7.0
new db1f26708d Build the wrapper job with Maven 4.0.0-rc-6
new c853752ef7 Download the wrapper distribution from Central, not the Google mirror
new c05b25dda5 Resolve from Central in CI, not the Google Cloud mirror
new 7f736da7ac Keep the mirror line, commented, rather than deleting it
The 4 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.github/ci-mimir-session.properties | 8 ++++++--
.github/workflows/maven.yml | 9 +++++++--
2 files changed, 13 insertions(+), 4 deletions(-)
(maven) 04/04: Keep the mirror line, commented, rather than deleting it
Posted by sl...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a commit to branch maven-4.0.x
in repository https://gitbox.apache.org/repos/asf/maven.git
commit 7f736da7acb7e2f49a5189b788ae28e380a218e1
Author: Sylwester Lachiewicz <sl...@apache.org>
AuthorDate: Tue Aug 4 12:58:50 2026 +0200
Keep the mirror line, commented, rather than deleting it
Restoring the Google Cloud mirror should be uncommenting one line, not
recovering it from history, if its sync latency ever stops being a problem.
Co-Authored-By: Claude Opus 5 (1M context) <no...@anthropic.com>
---
.github/workflows/maven.yml | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/.github/workflows/maven.yml b/.github/workflows/maven.yml
index a001b95a5e..658a76792b 100644
--- a/.github/workflows/maven.yml
+++ b/.github/workflows/maven.yml
@@ -36,9 +36,12 @@ env:
MIMIR_BASEDIR: ~/.mimir
MIMIR_LOCAL: ~/.mimir/local
MAVEN_OPTS: -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=./target/java_heapdump.hprof
- # No MVNW_REPOURL: the Google Cloud mirror of Central lags a fresh release by
- # a day or more, so the wrapper cannot fetch a just-published distribution
- # from it. Leaving it unset makes the wrapper download from Central itself.
+ # The Google Cloud mirror of Central lags a fresh release: 4.0.0-rc-6 was
+ # still a 404 there days after Central served it, so the wrapper could not
+ # fetch the distribution this workflow had just asked for. Unset, the
+ # wrapper downloads from Central. Uncomment to put the mirror back once its
+ # sync latency stops breaking release-day builds.
+ # MVNW_REPOURL: https://maven-central.storage-download.googleapis.com/maven2
jobs:
initial-build:
(maven) 03/04: Resolve from Central in CI, not the Google Cloud mirror
Posted by sl...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a commit to branch maven-4.0.x
in repository https://gitbox.apache.org/repos/asf/maven.git
commit c05b25dda594bde34f267838cc687045a7a5d3f6
Author: Sylwester Lachiewicz <sl...@apache.org>
AuthorDate: Tue Aug 4 12:53:12 2026 +0200
Resolve from Central in CI, not the Google Cloud mirror
The mimir session pointed dependency resolution at the same Google Cloud
mirror the wrapper used, and that mirror lags a fresh release: rc-6
artifacts were still 404 there days after Central served them.
Commented out rather than deleted, so restoring the mirror is one line if
its sync latency stops being a problem.
Co-Authored-By: Claude Opus 5 (1M context) <no...@anthropic.com>
---
.github/ci-mimir-session.properties | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/.github/ci-mimir-session.properties b/.github/ci-mimir-session.properties
index 26acd0f770..86f34f08b3 100644
--- a/.github/ci-mimir-session.properties
+++ b/.github/ci-mimir-session.properties
@@ -19,5 +19,9 @@
# do not waste time on this; we maintain the version
mimir.daemon.autoupdate=false
-# CI uses US Mirror
-mimir.session.mirrors=central(https://maven-central.storage-download.googleapis.com/maven2/)
\ No newline at end of file
+# CI used the Google Cloud mirror of Central, but that mirror lags a fresh
+# release: apache-maven-4.0.0-rc-6 was still a 404 there days after Central
+# served it. Resolving from Central directly is the difference between a
+# build that works on release day and one that waits for a mirror we do not
+# control.
+# mimir.session.mirrors=central(https://maven-central.storage-download.googleapis.com/maven2/)
\ No newline at end of file
(maven) 02/04: Download the wrapper distribution from Central, not the Google mirror
Posted by sl...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a commit to branch maven-4.0.x
in repository https://gitbox.apache.org/repos/asf/maven.git
commit c853752ef79700bc4738613c152c04e3b3d16be6
Author: Sylwester Lachiewicz <sl...@apache.org>
AuthorDate: Tue Aug 4 12:38:29 2026 +0200
Download the wrapper distribution from Central, not the Google mirror
MVNW_REPOURL pointed the wrapper at the Google Cloud mirror of Central,
which lags a fresh release: apache-maven-4.0.0-rc-6-bin.zip is a 404 there
while Central already serves it, so the initial-build job dies with
wget: Failed to fetch https://maven-central.storage-download.googleapis.com/maven2/org/apache/maven/apache-maven/4.0.0-rc-6/apache-maven-4.0.0-rc-6-bin.zip
Unsetting MVNW_REPOURL makes the wrapper fetch from Central, which always
has the version this workflow just asked for.
Co-Authored-By: Claude Opus 5 (1M context) <no...@anthropic.com>
---
.github/workflows/maven.yml | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/.github/workflows/maven.yml b/.github/workflows/maven.yml
index a794d48ebb..a001b95a5e 100644
--- a/.github/workflows/maven.yml
+++ b/.github/workflows/maven.yml
@@ -36,7 +36,9 @@ env:
MIMIR_BASEDIR: ~/.mimir
MIMIR_LOCAL: ~/.mimir/local
MAVEN_OPTS: -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=./target/java_heapdump.hprof
- MVNW_REPOURL: https://maven-central.storage-download.googleapis.com/maven2
+ # No MVNW_REPOURL: the Google Cloud mirror of Central lags a fresh release by
+ # a day or more, so the wrapper cannot fetch a just-published distribution
+ # from it. Leaving it unset makes the wrapper download from Central itself.
jobs:
initial-build:
(maven) 01/04: Build the wrapper job with Maven 4.0.0-rc-6
Posted by sl...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a commit to branch maven-4.0.x
in repository https://gitbox.apache.org/repos/asf/maven.git
commit db1f26708d3dd90b4d6874da7774afbcb5a37b3a
Author: Sylwester Lachiewicz <sl...@apache.org>
AuthorDate: Tue Aug 4 02:21:38 2026 +0200
Build the wrapper job with Maven 4.0.0-rc-6
Co-Authored-By: Claude Opus 5 (1M context) <no...@anthropic.com>
---
.github/workflows/maven.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.github/workflows/maven.yml b/.github/workflows/maven.yml
index 2cf3831ed0..a794d48ebb 100644
--- a/.github/workflows/maven.yml
+++ b/.github/workflows/maven.yml
@@ -72,7 +72,7 @@ jobs:
- name: Set up Maven
shell: bash
- run: mvn --errors --batch-mode --show-version org.apache.maven.plugins:maven-wrapper-plugin:3.3.4:wrapper "-Dmaven=4.0.0-rc-5"
+ run: mvn --errors --batch-mode --show-version org.apache.maven.plugins:maven-wrapper-plugin:3.3.4:wrapper "-Dmaven=4.0.0-rc-6"
- name: Prepare Mimir for Maven 4.x
shell: bash