maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Baptiste MATHUS (JIRA)" <j...@codehaus.org>
Subject [jira] Created: (SUREFIRE-529) forkMode none deprecated but given as an example in the debugging documentation
Date Wed, 12 Nov 2008 12:45:14 GMT
forkMode none deprecated but given as an example in the debugging documentation
-------------------------------------------------------------------------------

                 Key: SUREFIRE-529
                 URL: http://jira.codehaus.org/browse/SUREFIRE-529
             Project: Maven Surefire
          Issue Type: Bug
          Components: documentation
    Affects Versions: 2.4.3
            Reporter: Baptiste MATHUS
            Priority: Minor


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: 
bq. Can be "never", "once" or "always". *"none"* and "pertest" are also accepted for backwards
compatibility. 

Cheers.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message