Here's another clue:
When run against the jars, ProductVersionHolder.loadProperties() is able
to find the following resource:
/org/apache/derby/info/DBMS.properties
but not this one:
/org/apache/derby/info/tools.properties
-Rick
Kristian Waagan wrote:
Andreas Korneliussen wrote:
Andrew McIntyre wrote:
The test below that is reported as failing is the new test introduced
with DERBY-982, sysinfo_api.junit. This test passes on both my Mac OS
X and Windows XP system before and after commit. Does anyone have any
insight as to why the test may be failing in the Tinderbox
environment?
It failed for me when using jar-files in the classpath, however it
passed when using classes directory. The tinderbox uses jar-files.
The errors below are the same as I saw when I first tried the old test
for DERBY-982 (master based, not JUnit). When I think about it, I
think I also ran the new JUnit test from classes instead of jars.
Is this maybe a problem with sysinfo, or how it is run, and not the
test itself?
