В apache maven с плагином scala-maven-plugin, как отключить прерывание или пропуск подмодуля?

Question

У меня есть maven с несколькими подмодулями. Один из них (не последний) сломал тест:

mvn test -f pom.xml --fail-at-end -Pxxxx
...
*** RUN ABORTED ***
  java.lang.IllegalAccessError: tried to access method com.google.common.base.Stopwatch.<init>()V from class org.apache.hadoop.mapred.FileInputFormat
  at org.apache.hadoop.mapred.FileInputFormat.getSplits(FileInputFormat.java:312)
  at org.apache.spark.rdd.HadoopRDD.getPartitions(HadoopRDD.scala:204)
  at org.apache.spark.rdd.RDD$$anonfun$partitions$2.apply(RDD.scala:273)
  at org.apache.spark.rdd.RDD$$anonfun$partitions$2.apply(RDD.scala:269)
  at scala.Option.getOrElse(Option.scala:121)
  at org.apache.spark.rdd.RDD.partitions(RDD.scala:269)
  at org.apache.spark.rdd.MapPartitionsRDD.getPartitions(MapPartitionsRDD.scala:49)
  at org.apache.spark.rdd.RDD$$anonfun$partitions$2.apply(RDD.scala:273)
  at org.apache.spark.rdd.RDD$$anonfun$partitions$2.apply(RDD.scala:269)
  at scala.Option.getOrElse(Option.scala:121)
  ...
=============== Stopping Test Spark Context ==============
[INFO] 
[INFO] ------------------------------------------------------------------------
[INFO] Skipping spookystuff-core
[INFO] This project has been banned from the build due to previous failures.
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] ------------------------------------------------------------------------
[INFO] Skipping spookystuff-integration
[INFO] This project has been banned from the build due to previous failures.
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] ------------------------------------------------------------------------
[INFO] Skipping spookystuff-example
[INFO] This project has been banned from the build due to previous failures.
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] ------------------------------------------------------------------------
[INFO] Skipping spookystuff-assembly
[INFO] This project has been banned from the build due to previous failures.
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] ------------------------------------------------------------------------
[INFO] Skipping spookystuff-benchmark
[INFO] This project has been banned from the build due to previous failures.
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for spookystuff 0.6.2_2.11-SNAPSHOT:
[INFO] 
[INFO] spookystuff ........................................ SUCCESS [  2.341 s]
[INFO] spookystuff-test-resources ......................... SUCCESS [  1.009 s]
[INFO] spookystuff-mldsl .................................. FAILURE [ 23.527 s]
[INFO] spookystuff-core ................................... SKIPPED
[INFO] spookystuff-integration ............................ SKIPPED
[INFO] spookystuff-example ................................ SKIPPED
[INFO] spookystuff-assembly ............................... SKIPPED
[INFO] spookystuff-benchmark .............................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------

Этого не должно происходить, поскольку я использовал аргумент --fail-at-end, который должен заставить maven пытаться протестировать все подмодули независимо от сбоя теста или ошибки, возникшей при настройке фикстур.

(Вышеупомянутый феномен можно наблюдать на https://app.codeship.com/projects/166836/builds/48661715?pipeline=17f61f71-ddb0-43fb-9b38-2e827263fea5)

Мои вопросы:

1. Почему опция "отказ в конце" не действует?

2. Как инструктировать maven запускать все тесты во всех подмодулях, но при этом все равно терпеть неудачу при обнаружении какой-либо ошибки (то есть завершить работу с ненулевым кодом выхода)