You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org> on 2010/11/30 19:49:04 UTC

[jira] Created: (SUREFIRE-662) Forkmode=always rescans classpath in every forked vm

Forkmode=always rescans classpath in every forked vm
----------------------------------------------------

                 Key: SUREFIRE-662
                 URL: http://jira.codehaus.org/browse/SUREFIRE-662
             Project: Maven Surefire
          Issue Type: Improvement
          Components: JUnit 3.x support, Junit 4.7+ (parallel) support, Junit 4.x support, Maven Failsafe Plugin, Maven Surefire Plugin, TestNG support
    Affects Versions: 2.6
            Reporter: Kristian Rosenvold
            Priority: Minor


When using forkmode=always, the forked vm rescans the entire classpath every time, even though it ha been scanned within the surefire plugin itself. This should not be necessary and slows things down unecessarily.

-- 
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-662) Forkmode=always rescans classpath in every forked vm

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

Kristian Rosenvold closed SUREFIRE-662.
---------------------------------------

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

And r1045380 fixes for TestNG

> Forkmode=always rescans classpath in every forked vm
> ----------------------------------------------------
>
>                 Key: SUREFIRE-662
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-662
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: JUnit 3.x support, Junit 4.7+ (parallel) support, Junit 4.x support, Maven Failsafe Plugin, Maven Surefire Plugin, TestNG support
>    Affects Versions: 2.6
>            Reporter: Kristian Rosenvold
>            Assignee: Kristian Rosenvold
>            Priority: Minor
>             Fix For: 2.7
>
>
> When using forkmode=always, the forked vm rescans the entire classpath every time, even though it ha been scanned within the surefire plugin itself. This should not be necessary and slows things down unecessarily.

-- 
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] Issue Comment Edited: (SUREFIRE-662) Forkmode=always rescans classpath in every forked vm

Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/SUREFIRE-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=247480#action_247480 ] 

Kristian Rosenvold edited comment on SUREFIRE-662 at 12/13/10 2:30 PM:
-----------------------------------------------------------------------

Fixed for JUnit3 in r1045361

      was (Author: krosenvold):
    Fixed for JUnir3 in r1045361
  
> Forkmode=always rescans classpath in every forked vm
> ----------------------------------------------------
>
>                 Key: SUREFIRE-662
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-662
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: JUnit 3.x support, Junit 4.7+ (parallel) support, Junit 4.x support, Maven Failsafe Plugin, Maven Surefire Plugin, TestNG support
>    Affects Versions: 2.6
>            Reporter: Kristian Rosenvold
>            Priority: Minor
>
> When using forkmode=always, the forked vm rescans the entire classpath every time, even though it ha been scanned within the surefire plugin itself. This should not be necessary and slows things down unecessarily.

-- 
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] Commented: (SUREFIRE-662) Forkmode=always rescans classpath in every forked vm

Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/SUREFIRE-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=247470#action_247470 ] 

Kristian Rosenvold commented on SUREFIRE-662:
---------------------------------------------

Fixed for junit4 in r1045300. Junit4.7 fixed earlier.

> Forkmode=always rescans classpath in every forked vm
> ----------------------------------------------------
>
>                 Key: SUREFIRE-662
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-662
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: JUnit 3.x support, Junit 4.7+ (parallel) support, Junit 4.x support, Maven Failsafe Plugin, Maven Surefire Plugin, TestNG support
>    Affects Versions: 2.6
>            Reporter: Kristian Rosenvold
>            Priority: Minor
>
> When using forkmode=always, the forked vm rescans the entire classpath every time, even though it ha been scanned within the surefire plugin itself. This should not be necessary and slows things down unecessarily.

-- 
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] Commented: (SUREFIRE-662) Forkmode=always rescans classpath in every forked vm

Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/SUREFIRE-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=247480#action_247480 ] 

Kristian Rosenvold commented on SUREFIRE-662:
---------------------------------------------

Fixed for JUnir3 in r1045361

> Forkmode=always rescans classpath in every forked vm
> ----------------------------------------------------
>
>                 Key: SUREFIRE-662
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-662
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: JUnit 3.x support, Junit 4.7+ (parallel) support, Junit 4.x support, Maven Failsafe Plugin, Maven Surefire Plugin, TestNG support
>    Affects Versions: 2.6
>            Reporter: Kristian Rosenvold
>            Priority: Minor
>
> When using forkmode=always, the forked vm rescans the entire classpath every time, even though it ha been scanned within the surefire plugin itself. This should not be necessary and slows things down unecessarily.

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