IntelliJ Cannot Import sbt Project

Scala Problem Overview

I have upgraded IntelliJ to version CE 2017.3 from a CE 2017.2.5, and now I cannot build my sbt project. The build gets stuck on the first step:

"Build: sync
  MyProjName: syncing...
   dump project structure from sbt"

I have deleted the .idea directory and the the MyProjName/project/target directory. I did an sbt build from the command line, which worked. Then I started IntelliJ again and tried to import MyProjName/build.sbt as a project. I have also logged out/in. Did this several times. The import never progresses past this step.

I work behind a firewall, but I have checked my proxy settings, and they are correct and unchanged from the previous version (if this matters).

How can I troubleshoot / fix this?

The sbt version is 0.13.6. Scala plugin 2017.3.10.

From the log:

IDE: IntelliJ IDEA (build #IC-173.3727.127, 27 Nov 2017 09:32)
OS: Windows 7 (6.1, amd64) 
JRE: 1.8.0_152-release-1024-b6 (JetBrains s.r.o) 
JVM: 25.152-b6 (OpenJDK 64-Bit Server VM)

Scala Solutions

Solution 1 - Scala

I solved the sync issue following info here: https://youtrack.jetbrains.com/issue/SCL-13024

Key info is "It seems that sbt is trying to re-resolve 'sources' and 'docs' for sbt plugins that are not available at all. If properties to download "Library sources" and "sbt sources" are disabled, then time to dump the structure is reduced from 'forever' to less than 1 minute."

That is , in IntelliJ IDEA, clear the check box "Library sources" under "Project level settings" for Build Tools sbt in IDEA preferences. As shown in image below:

Solution 2 - Scala

The only way I could work around this was by running sbt clean compile in the SBT console/cmd line first, then refreshing the SBT project in IntelliJ.

Solution 3 - Scala

Open a terminal inside IDEA by pressing Alt F12 or use sbt shell
Run sbt - if it is first time it will take some time.
Run clean
Run compile - it will download dependencies you have in your project.
Close IDEA project (File -> Close Project) and open it again.

Note: if it asks to import in the right-bottom of the screen activate Enable auto-import, if you don't like to keep it enabled (like me) press Import, cancel the syncronyzation and then Refresh sbt project again. When you try to use import in the middle of a sync it gets stuck with dump project structure from sbt message.

The Refresh sbt project is located at this corner of the Build Sync window - highlighted below:

Solution 4 - Scala

I have not found a way to make this work in IntelliJ Idea CE 2017.3, so I have reverted to CE 2017.2.5

Solution 5 - Scala

IntelliJ appears to limit the efficiency of the already slow sbt update. I recommend using sbt-coursier instead. It was written specifically to improve dependency update time, and on one large project I'm involved in it improved dependency update time by about 2 orders of magnitude.

Uncheck "Use auto-import" in Preferences > Build, Execution, Deployment > Build Tools > sbt to prevent IntelliJ from auto updating imports on its own

Add addSbtPlugin("io.get-coursier" % "sbt-coursier" % "1.0.3") to your project's build.sbt file

Or install it globally in ~/.sbt/1.0/plugins/build.sbt

Run sbt update on the command line

If you see [error] java.lang.NoClassDefFoundError: org/vafer/jdeb/Console, then add the following to ~/.sbt/1.0/sbt-coursier.sbt.

import coursier.Keys._
classpathTypes += "maven-plugin"

_{See coursier issue #450 for more information about that error.}

(Optional) Re-enable auto-import from step 1, as subsequent transactional dependency updates may be faster.

Solution 6 - Scala

I meet the same problem！ I delete the directory ~/.sbt/0.13, then it works. You can delete the sbt directory you used.

Solution 7 - Scala

What worked for me was to increase the memory for SBT inside IntelliJ. On my Mac: preference -> Build, Execution, Depoyment -> sbt then change "Maximum heap size" from 768MB to 2048MB and then everything was successfully imported after few minutes.

Solution 8 - Scala

Custom SBT version works for me.

> IntelliJ IDEA Preferences -> Build,Execution,Deployment -> Build Tools -> sbt -> Launcher

Choose Custom

custom sbt screenshot

Solution 9 - Scala

For me, simply checking use sbt shell for both build and imports worked.

Solution 10 - Scala

Had an older checked out project causing this issue. Did the usual rm -rf .idea + re-import but it kept getting stuck. Tried all sorts of things, but when finally fixed it for me was not just deleting the top-level target folder, but instead doing

find . -name target -type d -exec rm -rf {} \;

Next open / import went flawlessly. (This was on 2018.1.5, 2018.1.6 and 2018.2 RC.)

Solution 11 - Scala

I have suffered from same problems after upgrade intelliJ to 2017.3 But it works fine now.

I think intelliJ couldn't pass the 'No proxy for' option to sbt. so, I added

> -Dhttp.nonProxyHosts="host1|host2"

option in File > Settings > Build, Excution, Deployment > sbt > VM parameters

Solution 12 - Scala

Simply unchecking 'sbt sources' did the trick for me

Solution 13 - Scala

I was also facing this issue. Below two configurations worked for me. I tried to confirm this setting in many new sbt projects, for all it worked.

(1) uncheck "Library sources" under "Project level settings" for Build Tools sbt in IDEA preferences (2) -Dhttp.nonProxyHosts="host1|host2" option in File > Settings > Build, Excution, Deployment > sbt > VM parameters

Solution 14 - Scala

I hit similar issue but found it's related to waiting for locks

~/.sbt/tool/sbt.boot.lock
~/.ivy2/.sbt.ivy.lock

Maybe if killing IntelliJ IDEA and no one will release the lock files, the issue is resolved after deleting locks files manually

Content Type	Original Author	Original Content on Stackoverflow
Question	radumanolescu	View Question on Stackoverflow
Solution 1 - Scala	civic.LiLister	View Answer on Stackoverflow
Solution 2 - Scala	JPotts	View Answer on Stackoverflow
Solution 3 - Scala	Marcio	View Answer on Stackoverflow
Solution 4 - Scala	radumanolescu	View Answer on Stackoverflow
Solution 5 - Scala	Cory Klein	View Answer on Stackoverflow
Solution 6 - Scala	xiang liu	View Answer on Stackoverflow
Solution 7 - Scala	marios	View Answer on Stackoverflow
Solution 8 - Scala	Huang Zehai	View Answer on Stackoverflow
Solution 9 - Scala	xerdink	View Answer on Stackoverflow
Solution 10 - Scala	nibblonian	View Answer on Stackoverflow
Solution 11 - Scala	Hsun	View Answer on Stackoverflow
Solution 12 - Scala	Gilad Tamar Tzemach	View Answer on Stackoverflow
Solution 13 - Scala	DistributedAI	View Answer on Stackoverflow
Solution 14 - Scala	Duke	View Answer on Stackoverflow