Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove more details about Maven 2 and old versions #654

Merged
merged 1 commit into from May 30, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
Expand Up @@ -76,7 +76,7 @@ mvn -DforkCount=0 verify
+---+
#{end}

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
Then all you need to do is debug Maven itself. Maven ships with a <<<mvnDebug>>> shell script that you can
use to launch Maven with convenient debugging options:

#{if}(${project.artifactId}=="maven-surefire-plugin")
Expand Down
Expand Up @@ -403,12 +403,3 @@ public class TestSuite {
therefore the threads will encounter race conditions when setting
properties, e.g. <<<baseDir>>>, which may lead to changing system properties
and unexpected runtime behaviour.

* Known issues and limitations

* <<<$\{surefire.forkNumber\}>>> propagation is not supported on Maven 2.x
(the variable will be resolved to null value all the time)

* <<<$\{surefire.forkNumber\}>>> is properly propagated within <<<workingDirectory>>>
since ${project.artifactId}:2.19, more details in
{{{https://issues.apache.org/jira/browse/SUREFIRE-1136}SUREFIRE-1136}}