In SDKMAN 3.3.1, sdk list will not work for any candidate names that previously worked:
sdk list grails
Stop! grails is not a valid candidate
sdk list gradle
Stop! gradle is not a valid candidate.
...
As you can see on the release build, all the tests passed which means that the list command definitely works. Also, when I enter sdk list grails, I get the following:
================================================================================
Available Grails Versions
================================================================================
3.1.0.RC1 3.0.0 2.3.5 2.1.4
3.1.0.M3 2.5.3 2.3.4 2.1.3
3.1.0.M2 * 2.5.2 2.3.3 2.1.2
* 3.1.0.M1 2.5.1 2.3.2 2.1.1
3.0.9 2.5.0 * 2.3.11 2.1.0
* 3.0.8 2.4.5 2.3.10 2.0.4
3.0.7 2.4.4 2.3.1 2.0.3
3.0.6 2.4.3 2.3.0 2.0.2
3.0.5 2.4.2 2.2.5 2.0.1
3.0.4 2.4.1 2.2.4 2.0.0
3.0.3 2.4.0 2.2.3 1.3.9
3.0.2 2.3.9 2.2.2 1.3.8
> * 3.0.11 2.3.8 2.2.1 1.3.7
3.0.10 2.3.7 2.2.0 1.3.6
3.0.1 2.3.6 2.1.5 1.3.5
================================================================================
+ - local version
* - installed
> - currently in use
================================================================================
Could I ask you to try flushing your candidates with sdk flush candidates, then opening a new terminal?
That fixed it. Thanks.
:+1:
I run sdk flush candidates but it cannot resolve the issue. Any suggestion?
Did you open a new terminal?
sdk ls | list not working
sdk ls grails works fine
below is the error
`
rammac:~ pillai$ sdk list
-bash: less is /usr/bin/less: No such file or directory
-bash: echo: write error: Broken pipe
`
You will need to use your package manager to install less.
I verified less is working fine.
I suggest moving this to the correct channel. We have a gitter user-issues channel for this sort of thing.
Most helpful comment
As you can see on the release build, all the tests passed which means that the list command definitely works. Also, when I enter
sdk list grails, I get the following:Could I ask you to try flushing your candidates with
sdk flush candidates, then opening a new terminal?