Skip to content

Commit 669cb09

Browse files
elharomichael-o
authored andcommitted
Remove more details about Maven 2 and old versions
1 parent 315d3e8 commit 669cb09

File tree

2 files changed

+1
-10
lines changed

2 files changed

+1
-10
lines changed

maven-surefire-plugin/src/site/apt/examples/debugging.apt.vm

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ mvn -DforkCount=0 verify
7676
+---+
7777
#{end}
7878

79-
Then all you need to do is debug Maven itself. Since Maven 2.0.8, Maven ships with a <<<mvnDebug>>> shell script that you can
79+
Then all you need to do is debug Maven itself. Maven ships with a <<<mvnDebug>>> shell script that you can
8080
use to launch Maven with convenient debugging options:
8181

8282
#{if}(${project.artifactId}=="maven-surefire-plugin")

maven-surefire-plugin/src/site/apt/examples/fork-options-and-parallel-execution.apt.vm

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -403,12 +403,3 @@ public class TestSuite {
403403
therefore the threads will encounter race conditions when setting
404404
properties, e.g. <<<baseDir>>>, which may lead to changing system properties
405405
and unexpected runtime behaviour.
406-
407-
* Known issues and limitations
408-
409-
* <<<$\{surefire.forkNumber\}>>> propagation is not supported on Maven 2.x
410-
(the variable will be resolved to null value all the time)
411-
412-
* <<<$\{surefire.forkNumber\}>>> is properly propagated within <<<workingDirectory>>>
413-
since ${project.artifactId}:2.19, more details in
414-
{{{https://issues.apache.org/jira/browse/SUREFIRE-1136}SUREFIRE-1136}}

0 commit comments

Comments
 (0)