[jira] Commented: (SUREFIRE-663) Allow custom Junit4 RunListeners to be specified

["Kristian Rosenvold (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/SUREFIRE-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=247279#action_247279 ] 

Kristian Rosenvold commented on SUREFIRE-663:
---------------------------------------------

The patch reformats the code in a code-standard that is not ASF. Also an integration test is a requirement. There is a org.apache.maven.surefire.junitcore.DiagnosticRunListener that should be usable to make an IT (it's in the 4.7 provider, you should be able to include that as a dependency within the actual IT)

Have a look at for instance surefire-integration-tests/src/test/resources/surefire-408-manual-provider-selection and the accompanying Surefire408ManualProviderSelectionIT.java for a nice starting point. 




> Allow custom Junit4 RunListeners to be specified
> ------------------------------------------------
>
>                 Key: SUREFIRE-663
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-663
>             Project: Maven Surefire
>          Issue Type: New Feature
>          Components: Junit 4.x support
>    Affects Versions: 2.6
>            Reporter: Matthew Gilliard
>         Attachments: surefire_junit4_listener.patch
>
>
> It would be nice to allow listing of FQCNs of Junit4 RunListeners in user's pom.xml so that they can add their own custom RunListeners.  Syntax would be the same as for TestNG, ie:
> <configuration>
>   <property>
>     <name>listener</name>
>     <value>list,of,FQCNs,implementing,org.junit.runner.notification.RunListener</value>
>   ...
> patch attached for surefire-junit4

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