You probably want to also set -DingnoreTestFailures
Or whatever it is called as those fail-at-end and fail-never just affect the overall result. If an individual module fails during "test" it will never get to "package" and the inter-module dependencies may not behave the same (jar files behave differently from target/classes) or may be missing (may be producing a war file to be consumed by an integration test module) IMHO you want both On Thursday, April 23, 2015, Mark Derricutt <[email protected]> wrote: > On 23 Apr 2015, at 17:12, Kevin Burton wrote: > > > My understanding , is that I can enable this, but then the result of the > > run is a successful build? Is that true? > > > > what’s the easiest way to set this up? > > You could use: > > mvn --fail-at-end > > which will run all modules regardless of if any fail, and only fail the > "build" at the end. > > or > > mvn --fail-never > > if you want to run everything, but have the build "succeed" and some other > process looks at the logs... > > Does that help? > > Mark > > -- > Mark Derricutt > http://www.theoryinpractice.net > http://www.chaliceofblood.net > http://plus.google.com/+MarkDerricutt > http://twitter.com/talios > http://facebook.com/mderricutt > -- Sent from my phone
