My coworker just found out that version 2.0 of surefire shows the correct error msgs.So it seems that error handling was changed between them and now it swallows the correct exceptions :-/ That would have saved a lot of time debugging this lol.
On Wed, Apr 8, 2009 at 7:45 AM, Tim <che...@gmail.com> wrote: > That's good to know :) > I can double check but that is probably not what is happening here since it > is defined in the parent pom as junit 4. > > > On Wed, Apr 8, 2009 at 7:15 AM, Jörg Schaible <joerg.schai...@gmx.de>wrote: > >> Hi Tim, >> >> Tim wrote at Mittwoch, 8. April 2009 14:05: >> >> > Unfortunately not. It seems however that surefire is actually giving the >> > wrong stacktrace. >> > When I run this via the cli using the classpath that surefire says it is >> > using I get a different exception. >> > It seems that a dependency was missing at that point. When I added it, I >> > got a new exception instead so it seems to be moving along. >> >> are you running surefire in a multi project where some modules use still >> JUnit 3 and the others JUnit 4? Remember, that a plugin is always loaded >> only once. So if you add for one module JUnit 4 as dep to the plugin, it >> does not help if the plugin has already be loaded elsewhere ... >> >> - Jörg >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> > > > -- > > Andy Warhol <http://www.brainyquote.com/quotes/authors/a/andy_warhol.html> - > "I am a deeply superficial person." > -- Fred Allen <http://www.brainyquote.com/quotes/authors/f/fred_allen.html> - "Washington is no place for a good actor. The competition from bad actors is too great."
