search

mvndaemon / homebrew-mvnd

This is a homebrew tap for mvnd, the Maven Daemon.
Apache License 2.0
7 stars 6 forks source link

How to handle mvnd 1.x and mvnd 2.x? #12

Open cstamas opened 2 weeks ago

cstamas commented 2 weeks ago

Currently we have one formula mvnd. And mvnd 1.0.0 is out, but soon will come mvnd 2.0.0 as well.

How we want to handle this?

@ppalaga @gnodet

gnodet commented 2 weeks ago

Same as Maven ?

cstamas commented 2 weeks ago

Ok, here in maven Formula I see 3.9.8 only: https://github.com/Homebrew/homebrew-core/blob/master/Formula/m/maven.rb

So it means once mvnd 2.0.0 out, it will replace mvnd 1.0.x (whatever version will be then current)?

AlexanderTerp commented 1 week ago

Related to this discussion:

With this change yesterday, brew install mvnd or brew upgrade mvnd will now install 2.0.0-beta, which also uses mvn 4.0.0-beta.

This seems undesirable? A few of us were surprised today when we saw that updating mvnd moved us off a stable release onto not one, but two betas. This caused some build issues for us and we needed to downgrade explicitly with mvnd@1.

gnodet commented 1 week ago

You can now install mvnd@1 to get the 1.x line. Homebrew is mostly focusing on installing the latest version. If you want to switch between versions, maybe using sdkman makes more sense.

cstamas commented 1 week ago

Updated README: https://github.com/apache/maven-mvnd/commit/df1001824e65fcc673561233e8ec2c83949d0868

paulochang commented 6 days ago

Hi @gnodet , I disagree, according to the documentation, homebrew should install the latest stable version. Beta versions should be tagged accordingly (https://docs.brew.sh/Acceptable-Casks#beta-unstable-development-nightly-or-legacy). Until a stable release of mvnd 2 is done, IMHO we should keep the version 1 as the main line.

This is also how it's handled in macports and sdkman

My projects stopped running today because of some sort of incompatibility with mvnd 2 and I expect this to be the case for the majority of the users.