You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Paul Gier (JIRA)" <ji...@codehaus.org> on 2010/05/14 18:43:12 UTC

[jira] Updated: (SUREFIRE-619) The surefire plugin should generate it's own classpath

     [ http://jira.codehaus.org/browse/SUREFIRE-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Gier updated SUREFIRE-619:
-------------------------------

    Fix Version/s: 2.6
         Assignee: Paul Gier

> The surefire plugin should generate it's own classpath
> ------------------------------------------------------
>
>                 Key: SUREFIRE-619
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-619
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: classloading, Maven Surefire Plugin
>    Affects Versions: 2.5
>            Reporter: Paul Gier
>            Assignee: Paul Gier
>             Fix For: 2.6
>
>
> I believe the surefire plugin would be improved if it generated it's own classpath instead of getting the test classpath from maven project.  This would allow the user better control over what is included in the classpath, and would actually simplify parts of the code for building the classpath.

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