Add babashka to sdkman.io package list

[rajcspsg]

Is your feature request related to a problem? Please describe.
Lot of JVM related SDKs can be installed via sdman and sdkman is getting popular nowadays. Add this amazing package to sdkman.io package list.

Describe the solution you'd like
The solution is easy way. We have to follow the vendor onboarding process here

Describe alternatives you've considered
Brew is not allowed in our organization. I would be nice to have multiple ways to have an SDK installed.

[borkdude]

Package managers are usually maintained by third parties. I only maintain the brew package and this is enough work as it is but if someone wants to add sdkman support, go for it!

[marc0der]

Package managers are usually maintained by third parties.

SDKMAN isn't a package manager but more of a download manager. Many of the organisations in the JVM space use our Vendor API to publish their new versions for download these days. You can read more about that on our website. You can also take a look at the SDKs we already support.

If you wire JReleaser into your build, you get publishing to SDKMAN for free, all you need is an access token.

We're completely open source and don't make profit out of the tool. It would be great to have you join us.

[borkdude]

I'm not interested right now in rewriting any of the infrastructure that is in place and has worked well for years.
What I like about the current approach is that I have a final moment in which I can say: now the Github release looks fine, let's make it public. When using JReleaser, I think I won't have that level of control anymore.

Let me just re-phrase stuff. I'm not interested in putting any effort in changing release infrastructure since I'm happy with how stuff currently works. But there are people who would like to download babashka with sdkman instead of Github actions. Given that:
What is the minimal effort that I or someone else can do to satisfy sdkman users, given that the binaries are already on github releases?

[aalmiray]

Understood. In that case, a direct REST call to Sdkman's API would be enough. Doesn't require any external tools other than bash but does require knowledge of the given endpoints and payload format.

OTOH, JReleaser requires 1 extra tool download (if running locally) or 1 extra GH action (if running on CI), plus 1 extra model file. With just 1 command (jreleaser publish) assuming binaries are already found at the expected location (tagged Github release).

[borkdude]

Thanks a lot. So I guess jreleaser could be used in an additional CI job that runs with a cron expression or so or is triggered otherwise, that would upload the Github release binaries to sdkman. Sounds good.

[aalmiray]

Correct. There’s one extra bit of information. I think right now the model expects binaries to be resolvable from the local filesystem before publication/announcing to sdkman can happen. This means downloading assets to a given location is a requirement. Luckily JReleaser has a download command that can do this but does come with a downside: “duplicate” asset defs. 1 url for download, 1 path for resolving the file for sdkman publication.

[lispyclouds]

I can try to take a stab as this over the weekend.