Bill Barker wrote:
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.
#4 seems like the most appropriate. But its not something I'm familiar with.
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
