mvnd 0.9.0 "destroys" the console about maven-mvnd HOT 8 OPEN

I got the same issue, and in fact this problem was solved after 1.0-m6-39/40, seems it only affect in the version range 0.9.0 to 1.0.0-m4.

Maybe you can solve this by update your mvnd.

If for a short time usage to mvnd 0.9.0 or 1.0.0-m4, you can manually run Ctrl + C to clear the wrong print like '^[[A', and then run CMD or bash or sh to restore the command line after this issue happended.

from maven-mvnd.

Yes, I can use 1.0.0. Usally I use Chocolatey to install mvnd. Is it possible to install 1.0.0 milestones with choco, too?

from maven-mvnd.

Yes, I can use 1.0.0. Usally I use Chocolatey to install mvnd. Is it possible to install 1.0.0 milestones with choco, too?

Em... I tried it but could only install mvnd up to 0.9.0 with Chocolatey...
Maybe the team just publish release version to Chocolatey repository, not the milestone versions.
That does bother.
I think downgrading to 0.8.2 is the best solution in this situation. In fact, I did use 0.8.2 before upgrading to 1.0-m6 for a long time.

from maven-mvnd.

@OLibutzki @GitPopcorn The release process has changed a bit with recent releases. If someone can provide a script that would automatically publish the release to chocolatey somehow, it could be integrated in https://github.com/apache/maven-mvnd/blob/master/build/release-publish.sh

from maven-mvnd.

Afaik, @johanjanssen provided the choco packages so far. Maybe he can help?

The scripts are located here: https://github.com/johanjanssen/ChocolateyPackages/tree/master/mvndaemon

Maybe @aalmiray (JReleaser) can help, too...

from maven-mvnd.

I think Chocolatey doesn't support beta/milestone version information in their tags. So to solve this I think I would need to create a new Chocolatey package with a different id, something like mvnd-beta. Or are there other ways?

Next to that I already indicated that I want to stop maintaining the Chocolatey package, as I don't use them myself anymore. So if someone wants to take over, let me know. I'm happy to maintain it until the end of the year, but after that I won't do it anymore.

from maven-mvnd.

In my opinion the best option is to include the choco publication in the mvnd release process - similar to homebrew and sdkman.

from maven-mvnd.

JReleaser can certainly help. As @johanjanssen mentioned the use of tags is tricky. I know for a fact that M and RC are treated specially, don't know about BETA and ALPHA.

Moreover, as Johan has states he'll no longer support the choco package someone else must take on the task.

from maven-mvnd.