Scalatest maven插件：错误：-c已被弃用很长时间，不再支持

Question

我使用scalatest-maven-plugin最新1.0版本，其中source code here。试图并行运行我的套房和使用以下配置：

<build><plugin> 
    <groupId>org.scalatest</groupId> 
    <artifactId>scalatest-maven-plugin</artifactId> 
    <version>1.0</version> 
    <configuration> 
     <reportsDirectory>${project.build.directory}/surefire-reports</reportsDirectory> 
     <junitxml>.</junitxml> 
     <filereports>WDF TestSuite.txt</filereports> 
     <htmlreporters>${project.build.directory}/html/scalatest</htmlreporters>      
     <parallel>true</parallel> 
    </configuration> 
    <executions> 
     <execution> 
      <id>test</id> 
      <goals> 
       <goal>test</goal> 
      </goals> 
     </execution> 
    </executions> 
</plugin></build> 

导致以下Maven构建错误：

[INFO] 
[INFO] --- scalatest-maven-plugin:1.0:test (test) @ myproject --- 
Exception in thread "ScalaTest-main" java.lang.IllegalArgumentException: ERROR: -c has been deprecated for a very long time and is no longer supported, to prepare for reusing it for a different purpos 
e in the near future. Please change all uses of -c to -P. 
     at org.scalatest.tools.ArgsParser$.checkArgsForValidity(ArgsParser.scala:46) 
     at org.scalatest.tools.Runner$.runOptionallyWithPassFailReporter(Runner.scala:857) 
     at org.scalatest.tools.Runner$.main(Runner.scala:827) 
     at org.scalatest.tools.Runner.main(Runner.scala) 

基本上scalatest - Maven的插件是通过-c到scalatest CLI而不是正确的-P ..或甚至更好-P10即使用的线程数。

如何通过Maven将-P10传递给scalatest进程？我试图直接在MAVEN_OPTS环境变量或Maven CLI中设置它，但它没有被拾取。

我也曾尝试配置scalatest - Maven的插件是这样的：

<configuration> 
    <argLine>-P10</argLine> 
</configuration> 

但此参数是传递给Java进程，而不是到Scalatest所以它失败了。

Answer 1

我创建了my own fork of the scalatest-maven-plugin，修复了并行问题，并将其版本化为1.1-SNAPSHOT我还必须修复构建等。我包括一个直接下载的编译压缩包版本scalatest-maven-plugin_1.1-SNAPSHOT.tar.gz

然后对其进行测试，分叉my own version of a scala-maven-example使用my own fork of the scalatest-maven-plugin和修改scalatest样本代码，以显示用于加载每个执行每个套件的第一测试套件和线程ID线程ID 。我还让当前的线程在每个点上休眠10秒，以查看发生了什么。所有scalatest套件都由单个线程加载，并行执行，如果并行启用。

这是使用<parallel>false</parallel>结果：

[INFO] --- scalatest-maven-plugin:1.1-SNAPSHOT:test (test) @ scala-maven-testing --- 
Discovery starting. 
** loading 'net.lockney.AcceptanceTest' Suite with ThreadId=1 
==> executing 'Simple thing state' test with ThreadId=1 
** loading 'net.lockney.MatcherExampleSuite' Suite with ThreadId=1 
** loading 'net.lockney.SimpleSpec' Suite with ThreadId=1 
** loading 'net.lockney.SimpleSuite' Suite with ThreadId=1 
Discovery completed in 19 seconds, 98 milliseconds. 
Run starting. Expected test count is: 8 
AcceptanceTest: 
As a user 
I want to be able to create a simple thing and implicitly start it 
So that I can then turn it off 
And see that it is stopped 
Feature: Simple thing state 
    Scenario: User stops thing when it's already on 
    Given An initialized thing, that has not been started 
    When User stops it again 
    Then We should see that it is stopped 
==> executing 'equality' test with ThreadId=1 
MatcherExampleSuite: 
- equality 
==> executing 'SimpleObject' should 'accept a String' test with ThreadId=1 
- string matchers *** FAILED *** 
    "something" did not end with substring "some" (MatcherExampleSuite.scala:29) 
SimpleSpec: 
SimpleObject 
- should accept a String 
- should even accept really long Strings 
==> executing 'An empty Set should have size 0' test with ThreadId=1 
... 
Run completed in 28 seconds, 300 milliseconds. 
Total number of tests run: 8 
Suites: completed 5, aborted 0 
Tests: succeeded 6, failed 2, canceled 0, ignored 0, pending 0 
*** 2 TESTS FAILED *** 

，这是使用<parallel>true</parallel>和<parallelThreads>10</parallelThreads>结果：

[INFO] --- scalatest-maven-plugin:1.1-SNAPSHOT:test (test) @ scala-maven-testing --- 
Discovery starting. 
** loading 'net.lockney.AcceptanceTest' Suite with ThreadId=1 
==> executing 'Simple thing state' test with ThreadId=1 
** loading 'net.lockney.MatcherExampleSuite' Suite with ThreadId=1 
** loading 'net.lockney.SimpleSpec' Suite with ThreadId=1 
** loading 'net.lockney.SimpleSuite' Suite with ThreadId=1 
Discovery completed in 30 seconds, 904 milliseconds. 
Run starting. Expected test count is: 8 
MatcherExampleSuite: 
SimpleSuite: 
AcceptanceTest: 
SimpleSpec: 
SimpleObject 
As a user 
I want to be able to create a simple thing and implicitly start it 
So that I can then turn it off 
And see that it is stopped 
Feature: Simple thing state 
==> executing 'An empty Set should have size 0' test with ThreadId=13 
==> executing 'SimpleObject' should 'accept a String' test with ThreadId=12 
==> executing 'equality' test with ThreadId=11 
... 
Run completed in 40 seconds, 706 milliseconds. 
Total number of tests run: 8 
Suites: completed 5, aborted 0 
Tests: succeeded 6, failed 2, canceled 0, ignored 0, pending 0 
*** 2 TESTS FAILED ***