You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Micah Whitacre (JIRA)" <ji...@codehaus.org> on 2006/08/25 22:42:48 UTC
[jira] Created: (MSUREFIRE-159) Surefire should provide a pluggable
means to specify a custom provider
Surefire should provide a pluggable means to specify a custom provider
----------------------------------------------------------------------
Key: MSUREFIRE-159
URL: http://jira.codehaus.org/browse/MSUREFIRE-159
Project: Maven 2.x Surefire Plugin
Issue Type: Bug
Affects Versions: 2.3
Reporter: Micah Whitacre
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
[jira] Updated: (SUREFIRE-141) Surefire should provide a pluggable
means to specify a custom provider
Posted by "Stephen Connolly (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Connolly updated SUREFIRE-141:
--------------------------------------
Priority: Blocker (was: Critical)
this should be a must fix 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: 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
[jira] Commented: (SUREFIRE-141) Surefire should provide a
pluggable means to specify a custom provider
Posted by "Jacek Furmankiewicz (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236404#action_236404 ]
Jacek Furmankiewicz commented on SUREFIRE-141:
----------------------------------------------
is there any timeline for this? We would like to start using non-Java BDD tools such as Cucumber (Ruby) or Lettuce (Python) instead of using typical JUnit for integration tests. This would mean writing either our own separate Mojo that would plug into the integration-test phase (or better) just adding a Surefire provider.
Thank you
> 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: 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
[jira] Updated: (SUREFIRE-141) Surefire should provide a pluggable
means to specify a custom provider
Posted by "Stephen Connolly (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Moved: (SUREFIRE-141) Surefire should provide a pluggable
means to specify a custom provider
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Closed: (SUREFIRE-141) Surefire should provide a pluggable
means to specify a custom provider
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MSUREFIRE-159) Surefire should provide a pluggable
means to specify a custom provider
Posted by "fabrizio giustina (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSUREFIRE-159?page=all ]
fabrizio giustina updated MSUREFIRE-159:
----------------------------------------
Priority: Critical (was: Major)
Fix Version/s: 2.4
Issue Type: New Feature (was: Bug)
> Surefire should provide a pluggable means to specify a custom provider
> ----------------------------------------------------------------------
>
> Key: MSUREFIRE-159
> URL: http://jira.codehaus.org/browse/MSUREFIRE-159
> Project: Maven 2.x Surefire Plugin
> Issue Type: New Feature
> Affects Versions: 2.3
> 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
[jira] Commented: (SUREFIRE-141) Surefire should provide a
pluggable means to specify a custom provider
Posted by "Arnaud Bailly (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_86906 ]
Arnaud Bailly commented on SUREFIRE-141:
----------------------------------------
In my case, I would like to add a custom provider for generating coverage information during testing. This would allow coverage reports to be generated without the need to rerun tests.
> 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
[jira] Commented: (SUREFIRE-141) Surefire should provide a
pluggable means to specify a custom provider
Posted by "Ralf Ebert (JIRA)" <ji...@codehaus.org>.
[ 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