Martin Desruisseaux wrote: > In this particular case the test failures in the "unsupported/tile" > module were not responsible for the initial build failure. They were > just unnoticed because commited while the build was already broken (by > me). Additionnaly they were not problematic because reproductible on > local machine like mine, so they were quite easy to comment-out. The > previous ScaleTest failure that initially broke the build was more > difficult because not reproductible on my machine. Thanks for the breakdown martin - was worried I messed it up. > As for handling the test for "unsupported" in a different fashion, it > is easy to configure Maven to ignore test failures (however > compilation error will continue to stop the build): > > http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#testFailureIgnore > > > > Do we want to ignore test failures in "unsupported" in all cases, or > only for some profiles? And if we ignore them, how will the developper > know which test failed (especially since we have the bad habit to dump > a lot of text to standard output, so it is quite difficult to spot the > surefire "test failure" messages in the middle of them). I think we want to ignore only for some profiles - indeed an example of how to do that would be very welcome.
Cheers, Jody ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
