billroper: (Default)
[personal profile] billroper
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. :)
This account has disabled anonymous posting.
If you don't have an account you can create one now.
HTML doesn't work in the subject.
More info about formatting

If you are unable to use this captcha for any reason, please contact us by email at support@dreamwidth.org

Profile

billroper: (Default)
billroper

January 2026

S M T W T F S
     1 2 3
4 5 6 7 8910
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 293031

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Jan. 30th, 2026 04:38 am
Powered by Dreamwidth Studios