Selfupdate dumps garbage on console. about sdkman-cli HOT 3 CLOSED

Ah, I saw this but didn't know how to reproduce. Glad you picked up on it.

from sdkman-cli.

The installation will be handled by a gvm-selfupdate script in the bin folder. This will prevent the gvm script from overwriting itself.

As part of this task, I'll also rework the installation of scripts by creating a zip file on the server side of all resources in the srv/scripts folder. The gvm-selfupdate script will then curl down the zip and unzip it into ~/.gvm/bin.

I was thinking about writing a gradle task to zip the files upfront, then pushing it to the heroku repo, but am very aware of the risk involved in forgetting to run this before pushing to heroku...

from sdkman-cli.

Lots of hacking to get this one working but I now have a descent (and clean) version up on the test environment. In short, we now have a /selfupdate endpoint that serves a script for downloading a zip binary containing the latest gvm scripts. This endpoint is curled, then invoked much like the installation procedure. This is done from within the selfupdate function in the gvm script.

The beauty of this is that the gvm script overwrite is now deferred to a different script, so we no longer see the annoying jumbled text when updating.

The downside is that to upgrade to this new version, the user will see jumbled text one last time on selfupdate.

from sdkman-cli.