So after spending the better part of the day (when not in meetings) sorting out yesterday's disastrous merge/rebasing of my branch, I discovered that it wouldn't work because of two mysterious known failures when running under the debugger in JDeveloper. One could be fixed by loading a non-standard version of a JAR file, but the other problem has no known fix.

The second mysterious failure is really annoying, since it's in the area that I was just asked to fix. I am told that it is not a problem, because I can always make a release build and install it on a temporary test machine to see how it is working -- and if it is not working, I suppose I can use 1970s debugging techniques to figure out why it isn't working.

Thus do we turn a debugging process that should have rapid turnaround into one that, well, does not.

I have complained about this. :)