You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Anders Hammar (JIRA)" <ji...@codehaus.org> on 2010/12/21 11:56:57 UTC

[jira] Created: (SUREFIRE-670) "surefire.junit4.upgradecheck" property not documented on site

"surefire.junit4.upgradecheck" property not documented on site
--------------------------------------------------------------

                 Key: SUREFIRE-670
                 URL: http://jira.codehaus.org/browse/SUREFIRE-670
             Project: Maven Surefire
          Issue Type: Improvement
          Components: documentation
    Affects Versions: 2.7
         Environment: n/a
            Reporter: Anders Hammar


I can't find any docs (example?) related to the "surefire.junit4.upgradecheck" property mentioned in the release mail. I think it should be added to the site for future reference.

>From release mail:
"Due to SUREFIRE-482 upgrading to surefire 2.7 may cause some
(incorrectly defined) tests to not be run any more. This should be
verified by running
mvn -Dsurefire.junit4.upgradecheck=true install at least once (this
can be run multiple times until you have fixed all issues)"

-- 
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-670) "surefire.junit4.upgradecheck" property not documented on site

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

Kristian Rosenvold closed SUREFIRE-670.
---------------------------------------

    Resolution: Fixed

Fixed in r1051580

> "surefire.junit4.upgradecheck" property not documented on site
> --------------------------------------------------------------
>
>                 Key: SUREFIRE-670
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-670
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 2.7
>         Environment: n/a
>            Reporter: Anders Hammar
>            Assignee: Kristian Rosenvold
>             Fix For: 2.7.1
>
>
> I can't find any docs (example?) related to the "surefire.junit4.upgradecheck" property mentioned in the release mail. I think it should be added to the site for future reference.
> From release mail:
> "Due to SUREFIRE-482 upgrading to surefire 2.7 may cause some
> (incorrectly defined) tests to not be run any more. This should be
> verified by running
> mvn -Dsurefire.junit4.upgradecheck=true install at least once (this
> can be run multiple times until you have fixed all issues)"

-- 
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-670) "surefire.junit4.upgradecheck" property not documented on site

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

Kristian Rosenvold updated SUREFIRE-670:
----------------------------------------

    Fix Version/s: 2.7.1

> "surefire.junit4.upgradecheck" property not documented on site
> --------------------------------------------------------------
>
>                 Key: SUREFIRE-670
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-670
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 2.7
>         Environment: n/a
>            Reporter: Anders Hammar
>            Assignee: Kristian Rosenvold
>             Fix For: 2.7.1
>
>
> I can't find any docs (example?) related to the "surefire.junit4.upgradecheck" property mentioned in the release mail. I think it should be added to the site for future reference.
> From release mail:
> "Due to SUREFIRE-482 upgrading to surefire 2.7 may cause some
> (incorrectly defined) tests to not be run any more. This should be
> verified by running
> mvn -Dsurefire.junit4.upgradecheck=true install at least once (this
> can be run multiple times until you have fixed all issues)"

-- 
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