Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Marco Vermeulen
    @marc0der
    :thumbsup:
    Cédric Champeau
    @melix
    hi there!
    Cédric Champeau
    @melix
    I have added:
    sdkman_beta_channel=true
    to my config, ran selfupdate force, opened new terminal, but I still can't see Java in the candidates
    Owen Worley
    @owenworley
    try flushing your candidates cache with sdk flush candidates, then opening a new terminal.
    @melix
    Cédric Champeau
    @melix
    tried it too
    without success
    Owen Worley
    @owenworley
    Not sure then sorry :(
    Marco Vermeulen
    @marc0der
    @melix so yes, sdk flush candidates and a new terminal must do it. if not, maybe you should double check that you have sdkman_beta_channel=true in ~/.sdkman/etc/config.
    Cédric Champeau
    @melix
    cat ~/.sdkman/etc/config 
    gvm_auto_answer=false
    gvm_auto_selfupdate=false
    gvm_insecure_ssl=false
    sdkman_auto_answer=false
    sdkman_auto_selfupdate=false
    sdkman_insecure_ssl=false
    sdkman_disable_gvm_alias=false
    sdkman_curl_connect_timeout=5
    sdkman_curl_max_time=4
    sdkman_beta_channel=true
    sdkman_debug_mode=false
    then I did sdk selfupdate force and sdk flush candidates and opened a new window and no luck
    it looks as if the sdkman_beta_channel was ignored
    and I'm still on the release channel
    Marco Vermeulen
    @marc0der
    it might be that your machine is using a login shell, which means logging in and out of your session.
    Marco Vermeulen
    @marc0der
    @/all I've fixed the OSX tr: Illegal byte sequence bug that we were seeing before. Version 5.1.14+116 fixes this. Please give it a spin and let me know if it fixes things.
    You might need to flush candidates and open a new terminal again after the upgrade, sorry folks...
    Owen Worley
    @owenworley
    will take a look when i have wifi, tethering atm
    Marco Vermeulen
    @marc0der
    👍
    Owen Worley
    @owenworley
    looks good to me :+1:
    Marco Vermeulen
    @marc0der
    can anyone else from the OSX camp confirm?
    ofadeyi
    @ofadeyi
    Screen Shot 2016-11-24 at 11.49.49.png
    Just tried installing java on OSX and it worked! Thanks very much!!
    Marco Vermeulen
    @marc0der
    :clap:
    Cédric Champeau
    @melix
    question
    sdk selfupdate force
    
    Updating SDKMAN...
    ######################################################################## 100.0%
    
    
    Successfully upgraded SDKMAN!
    
    Open a new terminal to start using SDKMAN 5.1.14+116.
    
    To join our BETA channel, simply follow the instructions on:
    
       http://sdkman.io/install.html
    is it normal it tells me how I can join the beta channel after selfupdate, when I have the config param set?
    actually I have 2 sdkman directories... mmm
    cat ~/.sdkman/etc/config 
    gvm_auto_answer=false
    gvm_auto_selfupdate=false
    gvm_insecure_ssl=false
    sdkman_auto_answer=false
    sdkman_auto_selfupdate=false
    sdkman_insecure_ssl=false
    sdkman_disable_gvm_alias=false
    sdkman_curl_connect_timeout=5
    sdkman_curl_max_time=4
    sdkman_beta_channel=true
    sdkman_debug_mode=false
    and
    cat ~/.sdkman.2/etc/config
    sdkman_auto_answer=false
    sdkman_auto_selfupdate=false
    sdkman_insecure_ssl=false
    sdkman_disable_gvm_alias=false
    sdkman_curl_connect_timeout=7
    sdkman_curl_max_time=10
    Marco Vermeulen
    @marc0der
    First question, this is a small bug that is fixed and will be released later today.
    The second directory seems to be some kind of backup you made.
    @melix the version you should see after opening the new terminal is 5.1.14+116
    Marco Vermeulen
    @marc0der
    @melix if you try a forced selfupdate this morning you should see the correct message 😉
    Henning Hoefer
    @hho
    Shouldn't sdk o upgrade all outdated candidates?
    hho@hho-pc3: ~
    ➜ sdk o
    
    Upgrade:
    gradle (3.2.1 < 3.3)
    kotlin (1.0.5-2 < 1.0.6)
    
    Upgrade candidate(s) and set latest version(s) as default? (Y/n): y
    
    Downloading: gradle 3.3
    
    In progress...
    
    ######################################################################## 100,0%
    
    Installing: gradle 3.3
    Done installing!
    
    
    Setting gradle 3.3 as default.
    
    hho@hho-pc3: ~
    ➜ sdk c
    
    Using:
    
    asciidoctorj: 1.5.4.1
    gradle: 3.3
    groovy: 2.4.7
    kotlin: 1.0.5-2
    maven: 3.3.9
    
    hho@hho-pc3: ~
    ➜
    If I run sdk o a second time, it correctly upgrades Kotlin. I'm on master+186.
    Marco Vermeulen
    @marc0der
    Yes it should, could I ask you to raise an issue on github please?
    Henning Hoefer
    @hho
    Sure, I just opened #522.
    Marco Vermeulen
    @marc0der
    Excellent thanks, could I ask you to include platform and shell details to?
    Henning Hoefer
    @hho
    What do you need? bash --version?
    Marco Vermeulen
    @marc0der
    Yes please, and the platform that your on.
    Henning Hoefer
    @hho
    sdk o again: sdkman/sdkman-cli#569
    Henning Hoefer
    @hho
    ~ $ sdk c
    WARNING: SDKMAN is out-of-date and requires an update. Please run:
    
      $ sdk update
    
    
    Using:
    
    gradle: 4.10.2
    java: 8.0.191-oracle
    kotlin: 1.3.0
    
    ~ $ sdk update
    No new candidates found at this time.
    
    ~ $ sdk selfupdate
    No update available at this time.
    
    ~ $ sdk v
    
    SDKMAN master+336
    Why that warning then?
    Marco Vermeulen
    @marc0der
    @hho the update command is similar to that of apt-get, it merely refreshes the local candidates cache (for now, although in the new sdkman it will also pull down versions for all candidates). We have moved away from doing this daily to a manual task that you need to do once a month, or manually if a new candidate was introduced
    selfupdate has a completely different purpose, it is or updating sdkman itself when a new version was released.
    We can probably improve the wording a little bit though, explaining why an update needs to be done.
    Feel free to raise a PR for this.
    Henning Hoefer
    @hho
    ah, that makes much more sense. thanks.
    How about doing it automatically instead of the warning? (not daily, only when the warning would appear)
    Marco Vermeulen
    @marc0der
    @hho that's pretty much how it worked before. we're trying to move away from all the continual internet access and moving towards how tools like apt or git work. You pull down remote state (like apt update, git pull) and then perform your work. this means we defer all updates until the very last moment and doing them in a more controlled bulk fashion. hope that makes sense.
    This was the first step we've taken, with many more to follow. We will be rolling out all this new behaviour as we rewrite the core components in Go.