forked from JetBrains/intellij-scala
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot download Hydra on sbt imported project with scalaHome set #37
Comments
dotta
added a commit
to dotta/intellij-scala
that referenced
this issue
Dec 23, 2017
…on. Fix triplequote#37 Our heuristic for extracting the scala version from the scala-compiler jar name may not work if the scala-compiler jar in the classpath has no version happended (this for instance can happen when importing an sbt project with the `scalaHome` setting set to point to a locally installed Scala distribution). The implemented solution consists in falling back to the module SDK Scala version if the version cannot be extracted from the scala-compiler jar name.
dotta
added a commit
to dotta/intellij-scala
that referenced
this issue
Dec 23, 2017
…on. Fix triplequote#37 Our heuristic for extracting the scala version from the scala-compiler jar name may not work if the scala-compiler jar in the classpath has no version happended (this for instance can happen when importing an sbt project with the `scalaHome` setting set to point to a locally installed Scala distribution). The implemented solution consists in falling back to the module SDK Scala version if the version cannot be extracted from the scala-compiler jar name.
dotta
added a commit
to dotta/intellij-scala
that referenced
this issue
Dec 23, 2017
…on. Fix triplequote#37 Our heuristic for extracting the scala version from the scala-compiler jar name may not work if the scala-compiler jar in the classpath has no version happended (this for instance can happen when importing an sbt project with the `scalaHome` setting set to point to a locally installed Scala distribution). The implemented solution consists in falling back to the module SDK Scala version if the version cannot be extracted from the scala-compiler jar name.
dotta
added a commit
that referenced
this issue
Dec 23, 2017
…tion Hydra Scala version detection heuristic fallbacks to module SDK version. Fix #37
dotta
added a commit
to dotta/intellij-scala
that referenced
this issue
Jan 6, 2018
…on. Fix triplequote#37 Our heuristic for extracting the scala version from the scala-compiler jar name may not work if the scala-compiler jar in the classpath has no version happended (this for instance can happen when importing an sbt project with the `scalaHome` setting set to point to a locally installed Scala distribution). The implemented solution consists in falling back to the module SDK Scala version if the version cannot be extracted from the scala-compiler jar name.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here is the build.sbt file to use to reproduce the issue:
Import the project into idea using the sbt build. Then, enable Hydra on the project and hit the Download button to fetch the Hydra artifacts. The following error is prompted:
Checking the idea.log provide the trail to understand the issue:
The issue is the regex we use to determine the scala version (see HydraVersions).
One possible fix is to look inside the
scala-compiler.jar
and read the version from thecompiler.properties
file if there is no version appended to thescala-compiler
jar.The text was updated successfully, but these errors were encountered: