for Windows and Linux
Use this tab to manage the behavior of the HotSwap mechanism.
|In this section, specify the behavior of HotSwap for Java: |
|Make project before reloading classes||This option controls action behavior. If it's turned on, the make process is performed before searching and reloading changed classes. |
|Enable "JVM will hang" warning||If this check box is selected, then, on an attempt to perform HotSwap while JVM is suspended, a warning about the possible hanging of this JVM will be displayed.|
|Reload classes in background||Select here whether you want to reload classes in background mode. This means, all progress messages will be displayed in a status bar.|
|Reload classes after compilation||Use the controls in this area to configure behavior of the HotSwap mechanism. |
- Always - select this option to have classes reloaded automatically.
- Never - when this option is selected, classes are not reloaded at all because the HotSwap mechanism is inactive.
- Ask - select this option to have IntelliJ IDEA ask you whether to reload altered classes or not.
|In this section, specify the behavior of HotSwap for Groovy: |
|Enable hot-swap agent for Groovy code||If this check box is selected, then a special agent will be added to the debugged process in order to enable hot-swap for Groovy code. |
If you don't want hot-swap, or this agent is getting in the way, clear this check box.
Enabling hot-swap agent may cause serialization problems in the debugged applications.
Last modified: 29 November 2017