Skip to content

Conversation

@pierre-rouleau
Copy link

  • The script was not creating the missing directory.
  • I also added printing the name of the directory where files were copied. New users (like me) may want to know where files went.

* The script was not creating the missing directory.
* I also added printing the name of the directory where files were copied.
  New users (like me) may want to know where files went.
@marc0der
Copy link
Member

Hi, the sdkman installer script already creates and populates the directory with binaries so this shouldn't be necessary if your SDKMAN is up to date. Can you share what version of SDKMAN you have on your machine?

@pierre-rouleau
Copy link
Author

pierre-rouleau commented Oct 29, 2025

I have: script: 5.20.0 native: 0.7.14 (macos aarch64)

However, I was under the impression that I did not need to have the original SDKMAN installed.
I installed the SDKMAN with the default method (curl -s "https://get.sdkman.io" | bash ) and all seems to be fine now.

However performing the extra checks as I added in the script are either required or the assumption about the existing presence should be identified somewhere to make it clear. No?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants