On Fri, 17 Feb 2006, Bill Barker <[EMAIL PROTECTED]> wrote: > Yup. It seems like our options are: > > 1) Change vmgump to run with Java 5, and hope that the ~50% coverage > we got last time has been fixed by their respective projects (it's > been awhile, so who knows :).
+1 and that's what I intended to do for a while now, just need to find tht time to do it. > 2) Change the 196 projects that <depend /> on JUnit to used > packaged-junit (ugh). > > 3) Change JUnit to build from a branch (not as bad as 2, but still > not what Gump is about) There will never be a release from that branch, so we can as well package up JUnit 3.8.1. If (1) doesn't work (because of other backwards incompatibilities in JUnit that may be there) we can selectivly use that. > 4) Just hope that the JUnit project comes to their senses, and > restores JVM 1.4 compatibility (not likely, given how extensive the > change seems to be). They won't. This is a conscious decision to break JDK 1.4 support and in many places they do so for good reasons. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
