Daniel John Debrunner wrote:
Daniel John Debrunner wrote:
Kristian Waagan wrote:
Hmm, the reason seems to be that derby.jar is not constructed correctly.
Guess it would be best to check the other jars as well...
Only the following files are included in derby.jar:
Might be my change, I'll look.
Fixed, svn 375975, never thought to check if an abstract unused class
was in the list of explicit classes to add to derby.jar.
Sorry,
Dan.
Thanks for fixing this so fast.
I updated to the newest revision and can confirm that derbyall does not
experience the problem reported anymore (when running from the jars).
The same should be seen when the next tinderbox test is run.
--
Kristian
