maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Rosenvold (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (SUREFIRE-141) Surefire should provide a pluggable means to specify a custom provider
Date Thu, 09 Dec 2010 22:09:58 GMT

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

Kristian Rosenvold closed SUREFIRE-141.
---------------------------------------

    Resolution: Fixed

Fixed in a *large* number of commits. API is not frozen until further notice.

> 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
>            Assignee: Kristian Rosenvold
>            Priority: Blocker
>             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

        

Mime
View raw message