activator new [nameoftheproject] play-scala).
Open ...> click the whole folder [nameoftheproject] >
root-buildselected by default. Don't change anything and click
From there some people use the IDE just to view/edit the project, while using the
sbt command line to compile/run/launch tests. Others prefer to launch those from within Intellij. It is required if you want to use the debug mode. Steps :
+in the top left > Choose
Play 2 Appin the list
Runmenu, or the buttons in the UI, you can now
Debugusing this configuration.
Runwill just launch the app, as if you did
sbt runfrom the command line.
Debugwill do the same thing but allow you to place breakpoints in the code to interrupt the execution and analyze what's happening.
This is an option global to the project, that is available at creation time and afterwards can be changed in the menu
Intellij IDEA >
Build, Execution, Deployment >
Build tools >
Project-level settings >
This option has nothing to do with the
import statements in the Scala code. It dictates what Intellij IDEA should do when you edit the
build.sbt file. If auto-import is activated, Intellij IDEA will parse the new build file immediately and refresh the project configuration automatically. It gets annoying quickly as this operation is expensive and tends to slow Intellij when you're still working on the build file. When auto-import is desactivated, you have to indicate manually to Intellij that you edited the
build.sbt and would like the project configuration to be refreshed. In most cases a temporary popup will appear to ask you if you would like to do so. Otherwise go to the SBT panel in the UI, and click the blue circling arrows sign to force the refresh.