commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <wbar...@wilshire.com>
Subject Re: [GUMP@vmgump]: Project commons-collections (in module jakarta-commons) failed
Date Sat, 11 Mar 2006 22:27:02 GMT

"Ted Husted" <ted@husted.com> wrote in message 
news:29012.780058156$1142071161@news.gmane.org...
> To whom it may engage...
>
<snip />
>    [junit] Running org.apache.commons.collections.TestAllPackages
>    [junit] Testsuite: org.apache.commons.collections.TestAllPackages
>    [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 0.107 sec
>    [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 0.107 sec
>
>    [junit] Testcase: warning(junit.framework.TestSuite$1): FAILED
>    [junit] No tests found in 
> org.apache.commons.collections.TestAllPackages
>    [junit] junit.framework.AssertionFailedError: No tests found in 
> org.apache.commons.collections.TestAllPackages
>

It seems that Ant already auto-detects JUnit-4, and in this case assumes 
that you've defined you're tests using pretty Annotations :).  In 
particular, it doesn't look for the:
  public static Test suite()
method in this case.  If anybody cares, the options that I can see are:

1) Talk to the Ant developers to add something like legacy="true" to the 
<junit /> task to force the old behavior even with JUnit-4 present.
2) Auto-detect JUnit-4 in the collections build.xml, and excecute a 
JUnit-4-compatible test-suite in this case.
3) Change the commons test-suite to be compatible with both JUnit-3&4.
4) Simply change the Gump descriptor to use junit3 to make the nags go away, 
and decide what you want to do about JUnit-4 support later.





---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message