On Sat, 11 Mar 2006, Bill Barker <[EMAIL PROTECTED]> wrote: > "Ted Husted" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] >> 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.
+1 for talking to the Ant developers and having them fix Ant. There will probably be more projects than commons collections that have their own suite method and expect it to be used. Even when Ant detects JUnit 4 it should still work with old-style tests the way it did before. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
