On Tue, 28 Feb 2006, <[EMAIL PROTECTED]> wrote:
> + Class junit4TestAdapterClass = null;
> + // Note that checking for JDK 5 directly won't work; under
> JDK 4, this will already have failed.
> + try {
> + if (loader == null) {
> + junit4TestAdapterClass =
> Class.forName("junit.framework.JUnit4TestAdapter");
> + } else {
> + junit4TestAdapterClass =
> Class.forName("junit.framework.JUnit4TestAdapter", true, loader);
> + }
> + } catch (ClassNotFoundException e) {
> + // OK, fall back to JUnit 3.
> + }
> + junit4 = junit4TestAdapterClass != null;
> +
I haven't looked into the implemenation of JUnit4TestAdapter so I
have to ask you 8-)
Even if I have JUnit 4 on my CLASSPATH I can still use JUnit 3 style
of tests (no annotations, naming conventions instead). Will this
patch still allow me to run those tests? Or will wrapping the tests
in a JUnit4TestAdapter force me to use annotations?
If JUnit would build in Gump (somebody seems to have forgotten to
check in a file) we'd already know since Gump will provide JUnit 4
to allmost all builds while most of them (including Ant) still use
JUnit 3 style tests.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
