You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Andreas Gudian (JIRA)" <ji...@codehaus.org> on 2013/01/29 09:17:13 UTC

[jira] (SUREFIRE-956) Let ${surefire.forkNumber} deliver unique values when used in parallel mvn builds

Andreas Gudian created SUREFIRE-956:
---------------------------------------

             Summary: Let ${surefire.forkNumber} deliver unique values when used in parallel mvn builds
                 Key: SUREFIRE-956
                 URL: https://jira.codehaus.org/browse/SUREFIRE-956
             Project: Maven Surefire
          Issue Type: Improvement
            Reporter: Andreas Gudian


Currently, ${surefire.forkNumber} is resolved to a unique value only for a single instance of the surefire execution. E.g. With {{forkCount=1}}, the place holder will always be resolved as {{1}}, even if tests are being executed concurrently by multiple instances of surefire within a {{mvn -T...}} build.

I'll start creating a path within the next couple of days... :)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] (SUREFIRE-956) Let ${surefire.forkNumber} deliver unique values when used in parallel mvn builds

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

Kristian Rosenvold closed SUREFIRE-956.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.14
         Assignee: Kristian Rosenvold

Applied in 0cd869ccec8dadb1c8b89baf8e8495819c236720, thanks for the patch!

Please close the pr
                
> Let ${surefire.forkNumber} deliver unique values when used in parallel mvn builds
> ---------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-956
>                 URL: https://jira.codehaus.org/browse/SUREFIRE-956
>             Project: Maven Surefire
>          Issue Type: Improvement
>            Reporter: Andreas Gudian
>            Assignee: Kristian Rosenvold
>             Fix For: 2.14
>
>
> Currently, ${surefire.forkNumber} is resolved to a unique value only for a single instance of the surefire execution. E.g. With {{forkCount=1}}, the place holder will always be resolved as {{1}}, even if tests are being executed concurrently by multiple instances of surefire within a {{mvn -T...}} build.
> I'll start creating a path within the next couple of days... :)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] (SUREFIRE-956) Let ${surefire.forkNumber} deliver unique values when used in parallel mvn builds

Posted by "Andreas Gudian (JIRA)" <ji...@codehaus.org>.
    [ https://jira.codehaus.org/browse/SUREFIRE-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318757#comment-318757 ] 

Andreas Gudian commented on SUREFIRE-956:
-----------------------------------------

Opened a github pull request for this: https://github.com/apache/maven-surefire/pull/22 :)
                
> Let ${surefire.forkNumber} deliver unique values when used in parallel mvn builds
> ---------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-956
>                 URL: https://jira.codehaus.org/browse/SUREFIRE-956
>             Project: Maven Surefire
>          Issue Type: Improvement
>            Reporter: Andreas Gudian
>
> Currently, ${surefire.forkNumber} is resolved to a unique value only for a single instance of the surefire execution. E.g. With {{forkCount=1}}, the place holder will always be resolved as {{1}}, even if tests are being executed concurrently by multiple instances of surefire within a {{mvn -T...}} build.
> I'll start creating a path within the next couple of days... :)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira