[SUREFIRE-529] forkMode none deprecated but given as an example in the debugging documentation

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.4.3
• Fix Version/s: 2.5
• Component/s: documentation
• Assignee: Paul Gier
• Reporter: Baptiste MATHUS
• Created: 12/Nov/08 06:43
• Updated: 20/Aug/09 11:42
• Resolved: 20/Aug/09 11:42

Description

On the maven-surefire-plugin website, on the following page about debugging: http://maven.apache.org/plugins/maven-surefire-plugin/examples/debugging.html

I guess the "mvn -DforkMode=none test" and "mvnDebug -DforkMode=none test" sentences should be updated to -DforkMode=never ?

In fact, in the forkMode property documentation: http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#forkMode, it is stated:

Can be "never", "once" or "always". "none" and "pertest" are also accepted for backwards compatibility.

Cheers.