OK, I've also tested with a simple maven projects and (as you mentioned) the artifacts are still deployed even after the tests fail.
Now irrespective of the color of the balls and what hudson does on its side, I expect mvn to behave the same on hudson and cmd-line. If maven does not deploy artifacts after a test failure then hudson should respect that choice. I don't really need hudson to "improve" the way maven works. This is just a huge design bug of the hudson-maven integration. And the behavior is not even optional. Then you were saying that the hudson maven plugin is crappy. But I like the way it works in a project with many modules where it discovers the modules and can do incremental builds. I'm very satisfied with it so far, it's just this bug that spoils it. -- View this message in context: http://maven.40175.n5.nabble.com/Running-tests-twice-and-the-build-success-status-tp3257693p3260403.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
