Jody Garnett a écrit : > 1) Upgrate maven-surefire-plugin to 2.3 (we are still using 2.2). [snip] > However the upgrate to maven-surefire-plugin 2.3 may not be completly smooth. > Last time we tried, we got test failures (probably related to classloaders) > and > had the downgrate to surefire 2.2. > If we have a volunter for upgrating surefire to 2.3 and make sure that all > tests > pass, then I think that switching to JUnit 4 would be painless.
maven-surefire-plugin 2.4 has been released and should be considered. I had a few problems running unit tests in a path with spaces for some unsupported[?] modules. Most vexing was that these unit tests passed in Eclipse and failed in Maven. The failures appeared to be poor surefire classloader behaviour combined with less than robust test code [our old friend File.toUrl()]. I was able to get consistent Eclipse-Maven behaviour by upgrading maven-surefire-plugin to 2.4, so it appears that the later version resolves some of the surefire classloader problems. I might add a Jira issue to find and fix all toUrl()/URLDecoder misuse. Given infinite time ... -- Ben Caradoc-Davies <[EMAIL PROTECTED]> Software Engineer CSIRO Exploration and Mining 26 Dick Perry Avenue, Kensington WA 6151, Australia ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
