You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by Knut Anders Hatlen <Kn...@Sun.COM> on 2006/10/17 21:24:22 UTC

Re: Workaround for running JUnit tests with the GUI runners

Kristian Waagan <Kr...@Sun.COM> writes:

> Hi Dyre,
>
> I think you can create a Jira for this, if you haven't already.
>
> The problem is that the GUI runners are using a custom classload to
> allow for dynamic reloading of the test classes.

I'm seeing this message in derby.log when I'm running with (any)
TestRunner:

DEBUG RAFContainerFactory OUTPUT: Caught exception when setting up
rafContainerConstructor

The tests don't fail because RAFContainerFactory falls back to the old
RAFContainer implementation. The exception seems to be a
ClassNotFoundException (cannot find RAFContainer4). Could it also be
caused by the custom classloader?

-- 
Knut Anders