Duke Listens!: Visit my main blog at MusicMachinery.com

This morning, I was fixing a bug using Netbeans.   Typical cycle: think, type, build, test.  However, the changes I made didn't seem to fix the bug.  I was nearly 100% sure that I'd identified the problem, but running the test was still showing the failure.  So another cycle of think, type, build and test.  Still, no dice.  Time to add some printlns - think, type, build, test. Woah! none of my debugging prints are showing up - what's going on? Dang!  The project I was working on was not my 'main' project in Netbeans. So when I hit build, it built the wrong project, so my changes were never being compiled. 

Netbeans should be smart enough to know that when you have multiple projects open and you are editing some source and you hit build you are likely to want to build the project related to the source that you just edited, and not the project that has no changes.  I'm probably bit by this at least once a week.  You'd think I'd learn my lesson, but I don't. Sigh.