Release 1.0.3?

[Tillerino]

New feature, improvement proposal

Hi there,

I am writing from downstream where we are having trouble building mvnd 1.0.2 with GraalVM 24: Groovy 4.0.22 does not support Java 24.

Now we are discussion all sorts of workarounds in NixOS/nixpkgs#407817, but I was wondering if you could do us a favor and just release mvnd 1.0.3 right now, which would solve our problem without any workarounds: On the mvnd-1.x branch Groovy was updated to 4.0.24, which suffices for Java 24.

Thanks!

[slawekjaranowski]

We have also release Maven 3.9.10 ... so we cen process also mvnd

@gnodet can you help to review open PR for 1.x

I can try to manage next release

[pmverma]

I would love to see this released so it work with maven 3.9.10

[cstamas]

We discovered a bug in 3.9.10, so we may want maven 3.9.11 first and then mvnd for it

[long76]

We discovered a bug in 3.9.10, so we may want maven 3.9.11 first and then mvnd for it

3.9.x last updated week ago(with all fixes). You can force 3.9.11 release?

[long76]

3.9.11 is here

[cstamas]

Yes, 3.9.10 was plagued with a nasty bug, so we rather waited for it

[pmverma]

1.0.2 was release almost a year ago. I really would like to see 1.0.3 released soon with maven 3.9.11

[lambersflorian]

Hi! Are there any plans to backport #1281 to 1.0.3? It would be nice to see this fix in the upcoming version, as we are occasionally facing the problem that the locks could not be acquired. We think that this fix might help us!

Thanks in advance!

[gsmet]

Hey there, any news for a 1.0.3? I would like to update the Quarkus build to 3.9.11 but I need a corresponding mvnd version.

Thanks!

[talios]

Naive question with mvnd - why is the maven version tied to releases of mvnd? I assume it currently ships with an embedded version, but would be nice to define a mvn.home path in mvnd.properties so we could independently update maven, or use a SNAPSHOT build alongside mvnd.

Either way, a release that supports 3.9.11 would be great.

[cstamas]

@talios mvnd 1.x uses Maven 3.x, and contains technical issues (hard work needed) to port things, as Maven 3 embedder is not really "reusability friendly". Hence, mvnd 1.x has literally a copy-paste of MavenCli + mvnd changes applied.

In mvnd 2.x (Maven 4) things are totally different, Maven 4 has new maven-cli done from ground up, and mvnd 2.x is literally just a "layer" around Maven core without any duplication.

In short: doing a mvnd 1.x release is a PITA, while doing a mvnd 2.x release is simple as simplest can be (up deps, shoot).

[cstamas]

mvnd 1.0.3 is in pipe, "soon" gonna happen. Very early after release of Maven 3.9.10 we got reports about nasty bug, hence we did quickly Maven 3.9.11... As explained above, doing mvnd 1.x release is a non trivial task, so we decided to simply skip buggy 3.9.10 and wait for 3.9.11.

[cstamas]

All pending mvnd 1.0.3-SNAP PRs merged, binaries built (for testing) can be get from here: https://github.com/apache/maven-mvnd/actions/runs/17556334805

Based on feedback, and going over issues we may release 1.0.3 soon.

[long76]

All pending mvnd 1.0.3-SNAP PRs merged, binaries built (for testing) can be get from here: https://github.com/apache/maven-mvnd/actions/runs/17556334805

Based on feedback, and going over issues we may release 1.0.3 soon.

run on current localRepository(all release dependecies exists) - OK run on empty localRepository(no any dependecies) - OK, no error of damaged dependency, .locks folder in repository created automatically

p. s. 15 projects(some depends from others) with modules was builded

[long76]

All pending mvnd 1.0.3-SNAP PRs merged, binaries built (for testing) can be get from here: https://github.com/apache/maven-mvnd/actions/runs/17556334805 Based on feedback, and going over issues we may release 1.0.3 soon.

run on current localRepository(all release dependecies exists) - OK run on empty localRepository(no any dependecies) - OK, no error of damaged dependency, .locks folder in repository created automatically

p. s. 15 projects(some depends from others) with modules was builded

https://github.com/apache/maven-mvnd/actions/runs/17618542498 still ok, Kubuntu 24.04

[cstamas]

We merged all outstanding PRs and triaged some issues as well: https://github.com/apache/maven-mvnd/milestone/44

Basically, 1.0.3 is imminent, unless someone yells (finds some blocker)

[ggjulio]

Hi! Are there any plans to backport #1281 to 1.0.3? It would be nice to see this fix in the upcoming version, as we are occasionally facing the problem that the locks could not be acquired. We think that this fix might help us!

Thanks in advance!

@cstamas, is there a way to have a backport of this too or is it too late for v1.0.3 ? It happen to us occasionally too and we're no where near to switch to mvn 4 as it's still not GA.

[cstamas]

It applied cleanly, so here it is, lets see what color it turns into: https://github.com/apache/maven-mvnd/pull/1427 Edit: it is 🟢

[long76]

It applied cleanly, so here it is, lets see what color it turns into: #1427 Edit: it is 🟢

https://github.com/apache/maven-mvnd/actions/runs/17672634756, no errors for me

[cstamas]

Vote: https://lists.apache.org/thread/vh03lvryc1nwd01bkmn4fn48ydvts71g

[hho]

Thank you for the release, but it doesn't seem to be available on Homebrew yet? I only get 1.0.2 when I try to install it as described in the README with brew install mvndaemon/homebrew-mvnd/mvnd@1

[cstamas]

Hm, @gnodet seems we switched to follow brew guidelines? I have

[cstamas@angeleyes ~]$ brew tap mvndaemon/homebrew-mvnd
==> Tapping mvndaemon/mvnd
Cloning into '/home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/mvndaemon/homebrew-mvnd'...
remote: Enumerating objects: 231, done.
remote: Counting objects: 100% (83/83), done.
remote: Compressing objects: 100% (53/53), done.
remote: Total 231 (delta 44), reused 53 (delta 22), pack-reused 148 (from 1)
Receiving objects: 100% (231/231), 35.42 KiB | 1.31 MiB/s, done.
Resolving deltas: 100% (108/108), done.
Tapped 2 formulae (18 files, 63.7KB).
[cstamas@angeleyes ~]$ brew info mvnd
==> mvndaemon/mvnd/mvnd: stable 1.0.3
Apache Maven Daemon
https://github.com/apache/maven-mvnd
Not installed
From: https://github.com/mvndaemon/homebrew-mvnd/blob/HEAD/Formula/mvnd.rb
License: Apache-2.0
==> Dependencies
Recommended: openjdk ✘
==> Options
--without-openjdk
	Build without openjdk support
[cstamas@angeleyes ~]$ brew info mvnd@1
==> mvndaemon/mvnd/mvnd@1: stable 1.0.2
Apache Maven Daemon
https://github.com/apache/maven-mvnd
Not installed
From: https://github.com/mvndaemon/homebrew-mvnd/blob/HEAD/Formula/[email protected]
License: Apache-2.0
==> Dependencies
Recommended: openjdk ✘
==> Options
--without-openjdk
	Build without openjdk support
[cstamas@angeleyes ~]$ 

So mvnd formula is now 1.0.3 and mvnd@1 is 1.0.2?

Also see https://github.com/apache/maven-mvnd/pull/1390

[gnodet]

@cstamas That was not really intended. I forgot to switch to the mvnd-1.x branch before running the publish scripts. I've reverted the change.

[cstamas]

Rechecked and now is ok: mvnd@1 is at 1.0.3, mvnd is back to 2.x.

@hho I think you can try again.

[hho]

Now it's working perfectly. Thank you both for the super quick response! ❤️