Hi, I noticed a recent commit caused a build failure in the jardriftcheck.
I put that in because of DERBY-6471 ( https://issues.apache.org/jira/browse/DERBY-6471); Create a regression test which will fail if classes from one Derby jar file leak into another jar file. At the time I tried to get input from the community, but there was no response, so I went ahead and put it in as an 'always' check. But if this check is too much work to run on the jars everytime we try to add a file (e.g. a test), then we can of course remove it from the buildjars target in build.xml, and for instance only run it before a release. Myrna
