title: Netbeans 7.3 annoyances
body: <p>I recently switched from Eclipse to Netbeans 7.3 and experiencing a lot of quirks and i'm wondering if anyone else experienced them and/or got a solution. Because of these 'problems' i'm considering switching back to Eclipse again but i'm in doubt because NB has a lot of good things too !</p>
  
  <p>These are the quirks:</p>
  
  <ul>
  <li>when creating a new Java class, and make some typo's e.g. somewhere in a method, NB does not recognize / display the errors directly, but after a very long wait or a restart of NB.
  This also happens to existing classes. </li>
  <li>background scanning tasks is sometimes stuck at 100%</li>
  <li>code completion does take forever. Don't even think about refactoring or renaming a class because it takes >3 minutes to scan the classpath (why, it's a new class for crying out load)</li>
  <li>hot-deployment: changes are not always synchronized correctly with the (Glassfish) server.
  Sometimes a complete undeploy and deploy is needed to reflect the changes made in the source.</li>
  <li>NB manipules my pom.xml and glassfish-web.xml: it adds a deploy hint to the pom.xml and also changes or removes the context-root in the glassfish-web.xml. Please stop doing this!</li>
  <li>Why o why can't i do a 'Fix imports' on my entire project. You <em>can</em> do a 'organize import' on the entire project, but this won't add the missing imports. See <a href="http://netbeans.org/bugzilla/show_bug.cgi?id=167031#c2" rel="nofollow">http://netbeans.org/bugzilla/show_bug.cgi?id=167031#c2</a></li>
  </ul>
  
  <p>Running NB 7.3 on Windows XP, 3GB RAM, 2+GHz cpu
  The project is a Java 7 maven project containing 12 modules / sub projects</p>