My gut feeling: some of your tests do have a problem. Since they hang overnight, this might be a timezone problem?
I once had a testcase who failed seemingly random. It turned out to be the difference between the internal Calendar.add(MONTH,1).add(MONTH, 1) whereas the test case compared this value with Calendar.add(MONTH, 2) And since 31.Jan + 1Month = 27.Feb + 1Month=27.March but 31.Jan + 2 Month = 31 March ... LieGrue, strub --- Rob Sargent <[email protected]> schrieb am Sa, 17.1.2009: > Von: Rob Sargent <[email protected]> > Betreff: release plugin run of test goal fails, though mvn test succeeds > An: [email protected] > Datum: Samstag, 17. Januar 2009, 23:38 > Thanks to Andrew Williams's post of Sep? 2007, I got > past this but > mvn release:prepare failed due to a unit test failure, even > though our tests > run cleanly via mvn test or mvn install > > Well acutally the test doesn't fail per se, rather it > hangs indefinitely > (overnight at least). > > maven-release-plugin:2.0-beta-7, testng spring injected > test doing some > nasty java/XA failure testing (read tempermental) but that > I don't believe > excuses the behaviour. Anyone else seen such a > discrepancy. > > > -- > View this message in context: > http://www.nabble.com/release-plugin-run-of-test-goal-fails%2C-though-mvn-test-succeeds-tp21521696p21521696.html > Sent from the Maven - Users mailing list archive at > Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: > [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
