slachiewicz opened a new pull request, #1709:
URL: https://github.com/apache/maven-mvnd/pull/1709
Every CI build currently prints, twice per job:
```
[INFO] Please upgrade to Mimir version 0.9.4 (you are using version 0.7.0)
[INFO] Resolving Mimir daemon version 0.7.0
```
It is only an INFO nag — nothing fails because of it — but 0.7.0 is well
behind.
## Coordinate change
`eu.maveniverse.maven.mimir:extension` was discontinued after 0.7.9. From
0.8.0 onward `extension3` is the single artifact covering both Maven 3 and
Maven 4, so the artifactId changes along with the version:
```xml
<extension>
<groupId>eu.maveniverse.maven.mimir</groupId>
<artifactId>extension3</artifactId>
<version>0.12.0</version>
</extension>
```
0.12.0 is the current release. Upstream tests against 3.9.11 and 4.0.0-rc-5;
the wrapper here uses 4.0.0-rc-5. Requirements are Java 17+, satisfied by the
Java 25 CI toolchain.
Going to 0.12.0 rather than the suggested 0.9.4 — the nag text is stale,
0.12.0 is what is actually current.
## Cache keys
Mimir 0.11.0 changed the local cache format and states existing caches must
be dropped and rebuilt. The GitHub cache keys therefore move from `mimir-*` to
`mimir2-*`; keeping the old prefix would let `restore-keys` pull a 0.7.0-format
cache into a 0.12.0 daemon. First run on each OS repopulates from scratch.
## Unchanged
`.github/ci-mimir-daemon.properties` needs no change —
`mimir.jgroups.enabled` is still a valid property
(`node/jgroups/.../JGroupsNodeConfig.java`), so LAN cache sharing stays off.
Placement of `extensions.xml` in `~/.m2/` is also still correct for Maven
4-rc-5+.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
