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. Thanks for investigating. Dan.
