Never mind, I think I fixed it.
The RuntimeMultiExceptionTest test was redirecting the System.out
stream, and there were 2 tests using that. When run in //, it's probable
that the redirection in the tearDown() method is done two quickly, while
the second test is using it, leading to the test failure.
I just disabled the parallel mode in the surefire plugin for the while
ldap-utils module, and it did the trick.
There might be a better way to manage that, like defining the test class
as not thread safe, but I'm not sure how to do it properly. If anyone
has an idea...
