Update resources on frame deactivation no longer builds in IntelliJ 9

I think that 'build on frame deactivation' feature makes sense only if build always completes within one-two seconds. Otherwise it may come to the
following: you change something, then switch to the browser, wait for several seconds, when switch back to IDEA to see that IDEA is still compiling
Java classes or the compilation fails because of errors. So we restricted that 'build' procedure to just copying of changes jsp/css/html files which
always proceed in a couple of seconds and cannot fail with errors. In order to update Java classes you can invoke 'Update Running Application' action
(Ctrl+F10), wait for its completion to see that there are no errors and then switch to the browser.

I have a tomcat run configuration.

In IntelliJ 8, I use to have Build on frame deactivation selected.
I could make a code change, alt-tab to the browser, wait a second or 2 while IntelliJ did its build, then refresh the page and all would be well.

It seems this behaviour has changed in IntelliJ 9.
The option has changed to Update resources on frame deactivation. I have to manually build/compile and only then can I alt-tab to the browser and refresh to get the changes.

Why was this behaviour changed and is it possible to add an option to make it do what it did in the past?

Thanks,
Nev

---
Original message URL: http://www.jetbrains.net/devnet/message/5264571#5264571

--
Nikolay Chashnikov
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

I haven't switched to 9.x yet (still using 8.x) but this change may make it so I never switch. I use build on frame deactivation all the time and the expected behavior is that it copies all resources over AND compiles my classes and hot deploys any changed classes (when using the debugger).

Did JetBrains get any complaints about the 8.x behavior? If not is seems like a random change for no apparent reason.

Not everyone has huge enterprisey web apps that takes many minutes to compile. Most of my apps only take a handfull of seconds to compile so build on frame deactivation works great.

I see what you are saying about apps that don't compile quickly (or compiles with errors); however, shouldn't it still be up to the user if they want to use this option? Maybe have 2 check boxes "Compile classes on frame deactivation" and "Copy resources on frame deactiviation". If my app takes a long time to compile I will simply uncheck the option, I am a big boy I can make this decision on my own, I don't need JetBrains to hold my hand:-)