Provide a choco package

[OLibutzki]

For Windows users it would be very convenient to ship mvnd via choco.

jbang already has a choco package, so this might be a good inspiration.

[ppalaga]

Contributions are highly welcome!

[famod]

FTR, this is what I found in jbang: https://github.com/jbangdev/jbang/tree/master/src/main/scripts/choco

[johanjanssen]

I've created a first version: https://github.com/johanjanssen/ChocolateyPackages/tree/master/mvndaemon

Please let me know if you have any remarks.

I've already submitted the package to Chocolatey. But they have to moderate it, which can take several weeks. After a while, the package hopefully becomes trusted and then I can release them and they become available after some automated checks.

[ppalaga]

That's a great news, thanks @johanjanssen!

It is fully OK if you prefer to maintain the files under your GH account but I am also open to a similar model we have with Brew: Michael Simons donated the Brew repo to mvndaemon GH organization and we gave him committer permissions there. This made it possible to somewhat distribute the work on various Brew issues that appeared in course of time. Esp. it allowed us to tune the release process that is now fully CI driven. I admit I have no idea how Chocolatey works and whether automated releases are possible at all.

[johanjanssen]

Good one, we can see how we do manage that over time. I don't mind too much, for me this was the quickest solution :). Just to make sure the package gets in the moderation queue at Chocolatey.

We can definitely automate it more, and I might even be able to use Michael's scripts for that. Thanks for the tip!

[johanjanssen]

The Chocolatey package is approved and generally available: https://chocolatey.org/packages/mvndaemon

[jglick]

It does not install a required DLL: #607

[johanjanssen]

It indeed only installs the mvndaemon itself and adds it to the path. When I created and tested the package it worked and it has quite some downloads without any remarks.

Unfortunately at this point in time I don't have a Windows machine available to test the current behavior and if needed change the package. If the mvndaemon team say that the DLL should always be installed and someone can change and test the Chocolatey scripts, then I can release a new version based on that.

[OLibutzki]

With mvnd 1.0.0 being released, this issue deserves some attention.

Maybe it's worth looking a JReleaser which supports building SDKMan, Homebrew and Chocolatey packages. From an external point of view, mvnd seems to be a good candidate for JReleaser.
/cc @aalmiray

// Edit
From the README file:

We’re looking for contribution to support MacPorts, Chocolatey, Scoop or asdf. If you fancy helping us…​

JReleaser supports all of them...

[OLibutzki]

Just realized that I pointed to JReleaser some time ago: #884 (comment)

#623 by @gnodet is related, too.

[aalmiray]

FWIW I believe mvnd accepted a PR more than a year ago that configured JReleaser for its releases. However, additional auth and vetting from ASF was required for using GH 3rd party actions such as oracle/setup-graal and jreleaser/release-action IIRC.

Perhaps that is no longer an obstacle. Happy to help get this done.

[johanjanssen]

My 2 cents: I no longer maintain the Chocolatey package. It's now maintained by @ajshastri ajshastri.