PROLOGUEI went searching YouTrack, doing my due diligence, for an issue (described below) before raising a feature request for IntelliJ's Compile Server facility.
I came across this issue, which describes slow compilation despite having the compile server enabled.
I echo here my comments and findings
If you are trying to make use of IntelliJ's Compile Server facility, say, to make you Red, Green... Refactor cycle go really fast, but can't seem to make it work or observe any speed gains, you may have overlooked an important step.
If when you make a change and click
Shift+F10and IntelliJ proceeds to 'make' your project, this applies to you.
The problem isn't to do how the Compile Server is configured; it has everything to do with your run configurations.
When you right-click a test or 'main' class, amongst other things, you have the option to 'Create Run Configuration' or 'Run' or 'Debug'; the first option creates a run configuration and pops-up a form to make changes before saving it (does not actually run it), where as the last two create run configurations for you implicitly, which IntelliJ reuses if you attempt to re-run/debug the same package/class/method element again later.
In ALL cases, not just these three, run configurations are created from a list of default configurations. The default for these three cases and many others, include the 'make' Before launch task.
This can be easily verified by playing around with the defaults and making implicit run configurations by right-clicking stuff as per normal.
But to address the slow compilation:
- Modify the default templates for the run configurations of interest - I changed Application, JUnit Test, Scala Console, ScalaTest and Spec2 - and removed the 'make' entry in the 'Before launch' section.
- Edit your existing run/test configurations, also removing the 'make' 'Before launch' section.
Unless you explicitly change your configuration defaults, right clicking on a test and selecting run will always generate a configuration with the 'make' task present.
Having just read all the blog posts from IntelliJ regarding the Compile Server and SBT's source-base change analysis, they clearly forgot to mention this important step.
Once removed, you can see when clicking
Runthe test runner starts spinning up immediately (assuming you're trying to run tests).
The only issue I have seen here (I have searched YouTrack for a mention of it to no avail) is if you make a change and hit
Shift+F10immediately, the test runner might fail as the test class is momentarily not on the classpath, that is, in that brief window between detecting the change and the compile server doing its thing.
Shift+F10) normally succeeds on the second attempt and it is still infinitely faster than waiting for a needless make to complete.
Now my IntelliJ seems truly amazing