[
http://jira.codehaus.org/browse/SUREFIRE-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=230086#action_230086
]
Ralf Ebert commented on SUREFIRE-141:
-------------------------------------
Also there is a nitpicking corner case where the provider cannot be guessed by
looking at the project dependencies: Building JUnit with Maven. JUnit has a
pom.xml ( http://github.com/KentBeck/junit/blob/master/pom.xml ) but will not
specify JUnit as dependency but still wants its tests to be executed using
'surefire-junit4'. A way to explicitly specify the provider would help here.
> 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: Backlog
>
>
> 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
