|Number of watchers on Github||750|
|Number of open issues||14|
|Average time to merge a PR||5 days|
|Open pull requests||50+|
|Closed pull requests||42+|
|Last commit||over 1 year ago|
|Repo Created||over 7 years ago|
|Repo Last Updated||over 1 year ago|
|Organization / Author||jetbrains|
|Do you use intellij-scala? Leave a review!|
|View open issues (14)|
|View intellij-scala activity|
|View on github|
|Fresh, new opensource launches 🚀🚀🚀|
Trendy new open source projects in your inbox! View examples
Plugin that implements Scala, sbt, Play 2, SSP and Hocon support in IntelliJ IDEA.
To get information about how to install and use this plugin in IDEA, please use IntelliJ IDEA online help.
If you have any question about the Scala plugin, we'd be glad to answer it in our developer community.
If you found a bug, please report it on our issue tracker.
If you want to contribute, please see our intro to the Scala plugin internals.
In order to take part in Scala plugin development, you need to:
Install IntelliJ IDEA 2017.1 or higher with a compatible version of Scala plugin
Fork this repository and clone it to your computer
$ git clone https://github.com/JetBrains/intellij-scala.git
Open IntelliJ IDEA, select
File -> New -> Project from existing sources, point to
the directory where Scala plugin repository is and then import it as sbt project.
When importing is finished, in order to get artifacts and run configurations for IDEA project, go to the Scala plugin repo directory and run
$ git checkout .idea
Preferences -> Build, Execution, Deployment -> sbt)
Use sbt shell for build and import
Global sbt settings -> JVM Options -> Maximum heap size, enter at least
Debugbutton to build and start a development version of IDEA with the Scala plugin.
To run tests properly, the plugin needs to be packaged. On the sbt shell:
fast tests can take over an hour. To get a quick feedback on project health, run the
> testOnly org.jetbrains.plugins.scala.lang.typeInference.*
The project is configured to build and run the typeInference tests with Travis CI, which you can enable in your forks. The full test suite can't currently be run because Travis doesn't allow builds to take that long.