IntelliJ Cannot Import sbt Project

Question

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)

what is the previous version of your idea . I have 2017.2.6. Aslo let us know the sbt, scala, java version. — user51, Dec 07 '17 at 14:59
Also, try to update scala plugin. The #2017.3.10 build have a couple of sbt related fixes. — niktrop, Dec 07 '17 at 15:54
For me it took almost an hour to go beyond this step on Ultimate 2017.3 — fR0DDY, Dec 07 '17 at 20:05
I am also facing the same problem. Glad to know that I am not alone. I will wait for an hour and two to see if moves past this step. — user238607, Dec 08 '17 at 09:43
Thanks @fR0DDY, I had to wait for two hours before it finished. Thanks for the tip that waiting is required for it to work. — user238607, Dec 08 '17 at 11:24
Mine exited in error after 11.5h. I will uninstall 2017.3 and try the previous version. — radumanolescu, Dec 09 '17 at 02:31
Maybe this is related https://youtrack.jetbrains.com/issue/SCL-13147 — Mark Canlas, Dec 18 '17 at 20:46
Radu, have you tried using the "sbt shell" import option? In my experience it's been faster in 2017.3 than the regular import. And you can see the output scroll by and see what it's stuck on (using the Build tab that will appear in the lower left). — Mark Canlas, Dec 21 '17 at 16:28
Nope, still takes ages to import a large multi-module project. — rabejens, Jan 23 '18 at 12:43
I am facing this same issue every time when I do fresh install of IntelliJ — nomadSK25, May 17 '19 at 07:13

score 94 · Answer 1 · answered Jan 27 '18 at 07:59

94

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:

answered Jan 27 '18 at 07:59

civic.LiLister

2,087
16
13

this is the only one that worked for me on community edition 2017.3.4 – nont Feb 08 '18 at 17:01
This worked for me on community edition 2017.3.4 on a 3G hotspot – vpipkt Feb 28 '18 at 17:24
This worked on 2018.1, just as a reminder you can still download sources when accessing its references(which for me looks faster as i will download them by demand). – Wesley Schleumer de Góes Apr 28 '18 at 17:03
Worked on 2018.1.4. – Henry Aug 23 '18 at 22:53
Works on 2019.1 for me. Thanks! – slugmandrew Apr 04 '19 at 06:35
Worked on 2019.2.4. Thanks! – Jiayi Liao Jul 25 '22 at 14:58

score 15 · Answer 2 · answered Dec 11 '17 at 19:36

15

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.

answered Dec 11 '17 at 19:36

JPotts

302
1
5

I have installed the latest 2017.3.3 (built 2018-01-15), and opened my project. It has started "dumping project structure from sbt", so I stopped that process and tried "clean compile" in the sbt console. Error: "No valid parser available" – radumanolescu Jan 22 '18 at 23:56
Refreshing can be done by clicking File -> Synchronize – bobismijnnaam Oct 01 '19 at 08:48

Marcio · Answer 3 · 2019-05-28T13:51:51.213

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:

This is working solution. This should be mark for answer. – Oomph Fortuity Jul 01 '19 at 12:46 — Oomph Fortuity, Jul 01 '19 at 12:46

score 6 · Answer 4 · answered Dec 11 '17 at 14:32

6

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

answered Dec 11 '17 at 14:32

radumanolescu

4,059
2
31
44

I added a new answer to this question. Let me know if what worked for me helps. – marios Jan 11 '18 at 00:09

Cory Klein · Answer 5 · 2018-11-27T01:58:38.283

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.

score 4 · Answer 6 · answered Dec 21 '17 at 12:18

4

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

answered Dec 21 '17 at 12:18

xiang liu

41
2

I just tried that, and for me it made no difference – radumanolescu Jan 23 '18 at 02:10
1

After deleteing I also increased the max heap as suggested in marios anwser. Then it took about 10 minutes (first time). I don't know if changing the Max heap helped or not. – ioleo Jan 24 '18 at 12:01

score 4 · Answer 7 · answered Jan 10 '18 at 21:16

4

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.

answered Jan 10 '18 at 21:16

marios

8,874
3
38
62

I have installed the latest 2017.3.3 (built 2018-01-15), and set the max heap to 4096 Mb. It still cannot finish "dumping project structure from sbt" – radumanolescu Jan 23 '18 at 00:02
Could take a while the first time. How long did you wait? – marios Jan 23 '18 at 03:38
10-20 min (this time). The previous time I installed 2017.3 I waited 11h. So I don't have a lot of patience for this particular bug. I have re-installed 2017.2 and it worked right away. – radumanolescu Jan 23 '18 at 03:41
1

I did delete the `.sbt/0.13/` dir. Then it took about 10 minutes (first time). I don't know if changing the Max heap helped or not. – ioleo Jan 24 '18 at 12:00
now that you mentioned it, I also deleted .sbt/0.13/. probably the deletion and the increase in memory did the work. – marios Jan 25 '18 at 04:22

score 2 · Answer 8 · edited Jan 21 '18 at 08:09

2

Custom SBT version works for me.

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

Choose Custom

custom sbt screenshot

edited Jan 21 '18 at 08:09

zx485

28,498
28
50
59

answered Jan 20 '18 at 16:35

Huang Zehai

21
1

score 2 · Answer 9 · answered Dec 18 '18 at 00:45

2

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

answered Dec 18 '18 at 00:45

xerdink

121
1
5

score 1 · Answer 10 · answered Jul 13 '18 at 23:31

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.)

score 0 · Answer 11 · answered Jan 11 '18 at 07:56

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

score 0 · Answer 12 · answered Jun 06 '18 at 12:23

0

Simply unchecking 'sbt sources' did the trick for me

answered Jun 06 '18 at 12:23

Gilad Tamar Tzemach

23
5

score 0 · Answer 13 · answered Nov 03 '18 at 16:14

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

score 0 · Answer 14 · answered Mar 09 '20 at 08:52

0

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

answered Mar 09 '20 at 08:52

Duke

1
3

IntelliJ Cannot Import sbt Project

14 Answers14

Linked