title: Grails & Netbeans: making changes without rerunning run-app
body: <p>Hey all,
  I'm just starting with Grails in Netbeans (6.9.1). I got a demo working, but each time i change a groovy file i need to build the project, and then select run (ie the equivalent of "grails build" and "grails run-app"). If there is already an instance running, I need to first shut that instance down.</p>
  
  <p>This seems wrong. It seems like i should be able to just change the groovy file, and it would get automagically reloaded. Isn't that the point of groovy?</p>
  
  <p>Is this actually how it's supposed to work in Netbeans? Without getting into an IDE war, do other IDEs do it better? everyone seems to rave about the Grails support in IntelliJ. Is it worth it?</p>
  
  <p>One last point... I noticed that a regular war maven project no longer automatically reloads on an F11 build. Could this be related?</p>
  
  <p>Thanks</p>
  
  <p>--Matthias </p>