How can I turn off HotSwap?

1

Every time I build, I get the following errors: 

2:10:17 PM Hot Swap failed
           com.beust.example.ExamplePackage: schema change not implemented;
           com.beust.example.ExamplePackage: Operation not supported by VM;
           com.beust.example.ExamplePackage: changes to class modifiers not implemented;
           com.beust.example.ExamplePackage: Operation not supported by VM;
           com.beust.example.ExamplePackage: delete method not implemented;
           com.beust.example.ExamplePackage: Operation not supported by VM;
           com.beust.example.ExamplePackage: changes to class modifiers not implemented;
           com.beust.example.ExamplePackage: Operation not supported by VM;
           com.beust.example.ExamplePackage: verifier detected internal inconsistency or security problem;
           com.beust.example.ExamplePackage: Verification error : verifier detected internal inconsistency or security problem;
           com.beust.example.ExamplePackage: verifier detected internal inconsistency or security problem;
           com.beust.example.ExamplePackage: Verification error : verifier detected internal inconsistency or security problem;
           com.beust.example.ExamplePackage: delete m... (show balloon)

This wouldn't bother me too much if these messages only appeared in the Event Log but they also appear in a giant red balloon in the lower left corner that pops up after every compilation and covers the console window. I have to dismiss this balloon after each compilation just so I can read the console. This is extremely annoying.

How can I get rid of that balloont? I don’t really care about these error messages.

Thanks.

2

Settings | Build, Execution, Deployment | Debugger | HotSwap | Reload classes after compilation, change to "Ask" or "Never".

3

That did it, thanks Dmitry!

I’d like to take this opportunity to point out that this red balloon is appearing at a terrible location, I think it should be moved at least to the right side of the screen (and is it really important to notify hotswap errors in that balloon? Seems like the event log should suffice).