You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Baptiste MATHUS (JIRA)" <ji...@codehaus.org> on 2008/11/12 13:45:14 UTC

[jira] Created: (SUREFIRE-529) forkMode none deprecated but given as an example in the debugging documentation

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

       

[jira] Updated: (SUREFIRE-529) forkMode none deprecated but given as an example in the debugging documentation

Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/SUREFIRE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Gier updated SUREFIRE-529:
-------------------------------

         Assignee: Paul Gier
    Fix Version/s: 2.5

> 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
>            Assignee: Paul Gier
>            Priority: Minor
>             Fix For: 2.5
>
>
> 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

       

[jira] Closed: (SUREFIRE-529) forkMode none deprecated but given as an example in the debugging documentation

Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/SUREFIRE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Gier closed SUREFIRE-529.
------------------------------

    Resolution: Fixed

Fixed in [r806246|http://svn.apache.org/viewvc?view=rev&revision=806246].

> 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
>            Assignee: Paul Gier
>            Priority: Minor
>             Fix For: 2.5
>
>
> 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