How to open SBT Tool Window in Intellij?

Question

This question may sound silly for you, but I have been searching the Internet for a while and couldn\'t find the answer. How can I open SBT Tool Window in Intellij (scala an

Answer 1

To be able to open SBT Console from View -> Tool Windows you first need to install the plugin required for it.

You can find the SBT plugin by searching for it under Settings -> Plugins -> Browse repositories

Plugin homepage: https://github.com/orfjackal/idea-sbt-plugin

Answer 2

In IntelliJ 2017.1, an sbt shell is integrated with the Scala plugin. You can open it from an icon on the sbt project view toolwindow, or from the "Tools" menu

Answer 3

You can either use above or simply use Alt+F12

Answer 4

In Intellij 16 SBT Console menu item no longer exists and in Debian 7 (XFCE) Alt-F12 doesn't work.

To run SBT console:

1. select View -> Tool Windows -> Terminal (for Alt-F12)
2. type sbt and console works

Answer 5

In Menu: View -> Tool Windows there should be two entries:

1. SBT
2. SBT Console

The first you can use to refresh IDEA project structure from SBT and view dependencies.

The second gives you a console where you can run sbt commands.

Update:

As Justin already aded:

As of IntelliJ IDEA 2017.1 Build #IC-171.3780.52 there is a new and (imho) better way:

(If you are working with an SBT project, that is)

When you open the SBT Tool Window, you will find a new scala terminal icon:

---

This will open an sbt console session with your sbt project import settings.

One major benefit is that you will actually (finally) get links to your code lines for compiler warnings and errors.

Answer 6

I had an issue where the sbt shell launcher was not on the bottom of the IDE and the sbt was not listed as an option under Tools. Discovered that the issue was after expanding a zip file of a scala project to my workspace, the build.sbt file was not in the root folder of the project structure, but nested one subfolder down. When importing this project into intellij it was not properly configuring it as an sbt project. After removing the project, exploding the zip in such a way that the build.sbt was in the root of the project and reimporting the issue was resolved.