Kristian, Well that's going to bomb out each failing module at the `test` phase in the lifecycle... which would ordinarily be OK, but most people have abused the lifecycle and will require the build to at least `package` in all modules... what you really want for this use case is something like failsafe:verify only for surefire and perhaps may even need to bind that to a phase after `install`
But it's probably better than what he's been tryinh On 3 August 2016 at 08:56, Kristian Rosenvold <krosenv...@apache.org> wrote: > -fae does not cut it ? > > 3. aug. 2016 00.45 skrev "Kevin Burton" <bur...@spinn3r.com>: > > > I have a COMPLEX multi module build. > > > > Like 250 sub-modules. > > > > If I do a big refactor the build stops after testing say 20 modules, > then I > > have to fix the build again, then it might get through 5 more modules, I > > have to keep repeating this process. > > > > What I want to do is to run tests on ALL modules and then show me which > > fail AT THE END. > > > > I also want to the build to FAIL at the end. > > > > There is -fn , but this cause the build to SUCCEED with failures and a > zero > > (success) exit code. > > > > Is there a way I can make it run ALL tests , across ALL modules, and then > > fail if ANY of the tests failed? > > > > Right now our CI system won't support maven failing with a zero exit > code. > > > > -- > > > > We’re hiring if you know of any awesome Java Devops or Linux Operations > > Engineers! > > > > Founder/CEO Spinn3r.com > > Location: *San Francisco, CA* > > blog: http://burtonator.wordpress.com > > … or check out my Google+ profile > > <https://plus.google.com/102718274791889610666/posts> > > >
