Stack trace is difficult to find when qtest fails during setup/teardown

When a qtest fails while executing one of the setup/teardown methods of a CLI driver (CliAdapter and its subclasses):

  public abstract void beforeClass() throws Exception;
  public abstract void setUp();
  public abstract void tearDown();
  public abstract void shutdown() throws Exception;

the original stack trace leading to the failure cannot be found easily.

Maven console shows a stack trace which doesn't correspond to the actual exception causing the problem but another one which in most cases does not contain the original cause.

The original stack trace is not displayed in the maven console and it is not in the target/tmp/logs/hive.log either. At the moment it goes to target/surefire-reports/...-output.txt.

The developer needs to search in 2-3 places and navigate back and forth to the code in order to find what went wrong.

Ideally the stack trace from the original exception should be printed directly in maven console.