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

我使用的是最新的1.0版本。尝试使用以下配置并行运行我的套件：

<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>

基本上，scalatest maven插件将

-c

传递到scalatest CLI，而不是正确的

-p

。。或者更好的是

-P10

，即要使用的线程数

如何通过Maven将

-P10

传递给scalatest进程？我已经尝试过在

MAVEN_OPTS

环境变量中设置它，或者直接在MAVEN CLI中设置它，但是没有得到响应

我还尝试过如下配置scalatest maven插件：

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

-P10

但是这个参数被传递给java进程，而不是Scalatest，所以它也会失败。

我创建了并行问题，修复了并行问题，并将其版本化为1.1-SNAPSHOT，我还必须修复构建，等等，它都被破坏了。我包括了一个可直接下载的编译tarball版本

然后，为了测试它，forked使用并修改scalatest示例代码来显示加载每个套件的线程Id和执行每个套件的第一个测试的线程Id。我还让当前线程在每个点上随机休眠10秒，以查看发生了什么。所有scalatest套件由单个线程加载，如果启用了并行，则并行执行

这是使用

false

得到的结果：

这是使用

true

和

10

得到的结果：

我创建并修复了并行问题，并将其版本化为1.1-SNAPSHOT，我还必须修复构建，等等，它都被破坏了。我包括了一个可直接下载的编译tarball版本

然后，为了测试它，forked使用并修改scalatest示例代码来显示加载每个套件的线程Id和执行每个套件的第一个测试的线程Id。我还让当前线程在每个点上随机休眠10秒，以查看发生了什么。所有scalatest套件由单个线程加载，如果启用了并行，则并行执行

这是使用

false

得到的结果：

这是使用

true

和

10

得到的结果：

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

[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 ***

[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 ***