You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2007/01/21 23:06:16 UTC
[jira] Moved: (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 ]
Brett Porter moved MSUREFIRE-159 to SUREFIRE-141:
-------------------------------------------------
Affects Version/s: (was: 2.3)
Fix Version/s: (was: 2.4)
2.4
Key: SUREFIRE-141 (was: MSUREFIRE-159)
Project: Maven Surefire (was: Maven 2.x Surefire Plugin)
> 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.4
>
>
> 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