by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    nafg
    @nafg
    Lately, importing SBT builds fails if "download SBT sources" is checked
    [error] (updateSbtClassifiers) lmcoursier.internal.shaded.coursier.error.FetchError$DownloadingArtifacts: Error fetching artifacts:
    [error] https://repo1.maven.org/maven2/org/webjars/envjs/1.2/envjs-1.2-sources.jar: not found: https://repo1.maven.org/maven2/org/webjars/envjs/1.2/envjs-1.2-sources.jar
    [error] https://repo1.maven.org/maven2/com/google/javascript/closure-compiler-externs/v20190513/closure-compiler-externs-v20190513-sources.jar: not found: https://repo1.maven.org/maven2/com/google/javascript/closure-compiler-externs/v20190513/closure-compiler-externs-v20190513-sources.jar
    This is true regardless of sbt shell setting
    Justin Kaeser
    @jastice
    @nafg which sbt version?
    nafg
    @nafg
    @jastice I guess ~latest, 1.3.8
    Justin Kaeser
    @jastice
    does it fail lately with change in sbt version, in scala plugin version, or change in dependencies?
    OlegYch
    @OlegYch
    Justin Kaeser
    @jastice
    thanks
    nafg
    @nafg
    @jastice maybe it's possible that if updateSbtClassifiers fails, it shouldn't cause it to lose everything else
    The same thing with project sources
    Isolate failures so they don't cascade, so to speak
    Justin Kaeser
    @jastice
    yeah not entirely trivial in the current implementation I think since it's just all based off the sbt task graph
    OlegYch
    @OlegYch
    nafg: disable 'get sbt sources'
    or exclude those dependencies
    or fix coursier
    or disable it
    nafg
    @nafg
    @jastice how does sbt communicate with intellij these days, is it writing an xml file to a known location?
    yeah it says Writing structure to /tmp/sbt-structure.xml...
    @jastice why not break it into separate commands and write each to a separate file, then don't assume if sbt failed everything is bad; take whatever xml files exist
    So there could be one xml file for each of {project,sbt}-{jars,sources}
    that way if any of them fail, the others, or at least those that ran first, are still there
    Justin Kaeser
    @jastice
    @nafg we might do that but it doesn't feel worth it to mitigate bugs limited to specific sbt versions tbh
    nafg
    @nafg
    @jastice it's not, often I might have some plugin or library dependency that depends on some artifact that for whatever reason doesn't publish a source jar
    Justin Kaeser
    @jastice
    yes, but only specific sbt versions cause this to be an error
    nafg
    @nafg
    I see
    Justin Kaeser
    @jastice
    so if you set project to 1.3.6 and disable automatic sbt upgrading it should work
    nafg
    @nafg
    what is automatic sbt upgrading
    Justin Kaeser
    @jastice
    image.png
    "allow overriding sbt version"
    nafg
    @nafg
    What does that do exactly?
    Justin Kaeser
    @jastice
    it upgrades the project-configured sbt version to use latest known by scala plugin when starting sbt shell
    nafg
    @nafg
    ah
    Maybe you should change the behavior to "forces to use sbt version latest supported by scala plugin" ;)
    So downgrade if necessary to 1.3.6 without requiring me to edit project/build.properties
    OlegYch
    @OlegYch
    or any other piece of software for that matter
    nafg
    @nafg
    ?
    OlegYch
    @OlegYch
    just saying 'override sbt version' should be removed
    Justin Kaeser
    @jastice
    the latest "supported" version is not necessarily known. We assume the latest available version is supported and usually has the least bugs. But every so often there's regressions 🤷‍♂️
    Arnaud Esteve
    @aesteve
    Is it easy to go back to 2019.3... (the current stable) after upgrading to 2020 EAP ? Sorry I wish I could tru dotty support but am a bit afraid of breaking everything
    Pavel Fatin
    @pavelfatin

    Hi! The blog post says:

    You can always select EAP or Release to revert to a more stable build; alternatively, you can download any Scala plugin build from https://plugins.jetbrains.com/plugin/1347-scala/versions.

    So, should be relatively easy. And, in any case, it should be possible to download and install any desired version of the Scala plugin manually.

    Arnaud Esteve
    @aesteve
    Thanks I missed that, my bad
    It's the list of unavailable plugins that frightened me a bit
    Wojtek Pituła
    @Krever
    Jetbrains Toolbox works very well for me. it allows you to install any intellij versions next to each other. So I have EAP as default and stable as backup
    Pavel Fatin
    @pavelfatin
    If you don't yet use the IDEA EAP, you can download and install it separately, so that the experiments won't affect your main IDEA installation at all. The Toolbox is another option, good point.
    Oron Port
    @soronpo
    The toolbox is great
    Arnaud Esteve
    @aesteve
    Ok, I'll try the toolbox then! thanks
    Arnaud Esteve
    @aesteve
    Capture d’écran 2020-03-18 à 11.48.51.png
    I'm probably still doing something wrong => 2020 EAP + nightly Scala plugin
    Pavel Fatin
    @pavelfatin
    @Krever We've included a mention of the Toolbox App in the post. Thanks for the useful tip!