Am 15.07.2012 01:19, schrieb Wayne Fay: >> 1. What does the maven-surefire-plugin exactly do? It still fails, but >> not so much like without it. > You were already using Surefire, you just had not declared a specific > version of the plugin to use, so you were probably using an earlier > version that might have had a bug which is resolved in 2.12, or > something along those lines.
Ok, I checked this with some more tests playing around with versions. During these test I fall back in a state where the count of occurrence of errors differs again. Well, after digging some more, I think, I know now whats going wrong. Looks like I was trapped because of an old doctrine: Never use space charaters in paths! Maven do everthing well, don't care if I added the surefire snipplet or not. But eclipse don't do. So further discussions goes to another list. ;) If someone else is interested, I posted a bug-report at eclipse bugzilla (ID 385223). It can be found here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=385223 >> 2. Is there a way to avoid running tests with maven depends on the OS if >> I reach a level where >> no independent solution exists like loading a C-lib for example, don't >> care if it is a good idea? > Stephen already answered this one. Add code which tests for the OS and > bails (with a warning) if this test cannot be executed in the current > OS. Checked this too. That's what I am looking for and it works perfect after a little tweaking and customizing. And for those guys, that reached this thread to get a solution for the I/O problem, which wasn't part of this thread, should take a look at package java.nio.file. It is available since 1.7. Thanks guys! --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org