So we are on the same way. Shortly speaking both options should build modules in the same way but the exit code should be a difference. This is problem in my company: We want to execute all unit tests of all modules but the compiler should not complain since the classes are pretty consistent and can be compiled. We want to get entire picture of all unit tests and Exit Code should be 1 due to the tests fail.
On Fri, Feb 2, 2018 at 9:21 AM, Robert Scholte <[email protected]> wrote: > I have the same expectations as Arnaud > > On Thu, 01 Feb 2018 13:55:20 +0100, Arnaud Héritier <[email protected]> > wrote: > > yes I think I agree >> my expectation would be >> >> -fae,--fail-at-end Only fail the build afterwards; >> allow all non-impacted builds to continue >> >> 0 if no problem, 1 if any module failed >> >> -ff,--fail-fast Stop at first failure in >> reactorized builds >> >> 0 if no problem, 1 if failed >> >> -fn,--fail-never NEVER fail the build, regardless >> of >> project result >> >> Always 0 >> >> >> On Thu, Feb 1, 2018 at 1:06 PM, Tibor Digana <[email protected]> >> wrote: >> >> I think this is bug (mvn --fail-at-end) because intermediate modules are >>> skipped. Unlike --fail-never runs all modules but returns exit 0. I want >>> exit 1 with --fail-at-end . >>> >>> WDYT? >>> >>> Cheers >>> Tibor >>> >>> >> >> > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
