Peter Johnson wrote:Yes, capture the full mvn output when you used -X and attach that output to the post.
The other thing I would try is to remove unit test classes one a a time until the mvn build doesn't fail. It could very well be that one of the tests is causing this issue and by removing them one at a time, you should be able to identify the bad test class. Once you have the test class identified, do the same with the test methods.
Peter Johnson wrote:Wow, that's a new one to me. Try running with mvn with -X and see if it provides any additional information. (I assume that none of your tests are calling System.exit()...)