I noticed a recent commit caused a build failure in the jardriftcheck.
Hi Myrna, Thanks for noticing this. I think the problem is that I updated sane.derbyTesting.jar.lastcontents, but didn't update insane.derbyTesting.jar.lastcontents (oops).
But if this check is too much work to run on the jars everytime
No, I think it's a good tool, it's not too much work. I just always build sane, and so I didn't think about the insane build. I'll get it fixed straightaway. bryan
