You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stephen Connolly (JIRA)" <ji...@codehaus.org> on 2010/08/10 12:58:33 UTC

[jira] Updated: (SUREFIRE-141) Surefire should provide a pluggable means to specify a custom provider

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

Stephen Connolly updated SUREFIRE-141:
--------------------------------------

    Fix Version/s:     (was: Backlog)
                   2.7

Putting in the bucket for 2.7

> Surefire should provide a pluggable means to specify a custom provider
> ----------------------------------------------------------------------
>
>                 Key: SUREFIRE-141
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-141
>             Project: Maven Surefire
>          Issue Type: New Feature
>            Reporter: Micah Whitacre
>            Priority: Critical
>             Fix For: 2.7
>
>
> The current way that surefire determines which provider to use is hard coded and based on a project's dependencies.  I would like to write a custom surefire-provider and be able to specify to use that provider without having to patch the surefire plugin.  In my case I want to write a surefire-provider that will run Eclipse PDE Junits which wouldn't neccessarily have a specific dependency listed

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