-
-
Notifications
You must be signed in to change notification settings - Fork 632
FAQ
Many such circumstances are caused when organisations and countries block access to the free and open internet. Our services are hosted on Digital Ocean in the US and may not be accessible in such restrictive environments. If you have such issues, we recommend using a VPN or proxy to bypass these restrictions.
Adding a new Version to an existing Candidate on SDKMAN is as simple as raising a pull request on our Database Migrations project. When the PR has been reviewed, approved and merged it will be run against our database making it available for all our users.
There is a chance it might conflict with the built-in script archlinux-java that comes with your distribution of ArchLinux. Run archlinux-java unset then remove all versions of Java from the default locations. Afterwards, install the desired versions with SDKMAN and use the java versions installed at $HOME/.sdkman/candidates/.
The java_home tool is a system-level tool provided by OSX. On the other hand, SDKMAN is a userspace tool that operates on your home folder only. These tools are mutually exclusive and can't be used together; java_home can only control what has been installed through OSX's own package manager and doesn't know about SDKMAN. Since SDKMAN already controls the setting of the JAVA_HOME variable, there is no need for using java_home.
The progress bar is part of curl, which we use for our scripts. To prevent the progress bar from being displayed, you can add a .curlrc file to the user home directory (~/.curlrc) and fill it with the following content: --no-progress-bar.
If this is not enough for you, you can also silence curl with the content -s in the same file.
If your questions haven't been answered, please feel free to join the SDKMAN Slack and get help in the user-issues channel.