Daniel John Debrunner wrote:
Michelle Caisse wrote:
I was using 10.2.1.1.
I see the same failure as you.
It's because the policy file is not setup to handle derbyTesting.jar
being in a different folder to derby.jar etc.
It's actually nothing to do with JUnit, you will see problems running
tests with the old harness.
I'm very suprised no-one has seen this before, since I thought there
have been several reports of derbyall passing against 10.2.1.1.
For the jobs doing nightly testing on the 10.2 branch we did a short
term workaround by copying derbyTesting.jar to its old location, to
avoid other changes. So, thats why it hasn't failed in those tests.
Vemund
