[
https://issues.apache.org/jira/browse/SUREFIRE-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969584#comment-14969584
]
Grzegorz Grzybek commented on SUREFIRE-1095:
--------------------------------------------
Thanks for hint - it worked with:
{code:xml}
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.19</version>
<dependencies>
<dependency>
<groupId>org.apache.maven.surefire</groupId>
<artifactId>surefire-junit47</artifactId>
<version>2.19</version>
</dependency>
</dependencies>
</plugin>
{code}
Description is not important for me - but I guess it was introduced on purpose.
Thanks for help.
> NPE in RunListener
> ------------------
>
> Key: SUREFIRE-1095
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1095
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support
> Affects Versions: 2.17
> Environment: Tested on Mac, using Maven 3.1, Java 7
> Reporter: Andrea Arcuri
> Assignee: Tibor Digana
> Fix For: 2.18
>
>
> In the surefire plugin, it is possible to specify one or more RunListener
> when running tests with JUnit.
> However, it does not look like the listener is properly called by the plugin.
> In particular, there is a problem with the method:
> public void testRunStarted(Description description)
> it's javadoc at
> http://junit.sourceforge.net/javadoc/org/junit/runner/notification/RunListener.html#testRunStarted%28org.junit.runner.Description%29
> states:
> "Parameters:
> description - describes the tests to be run "
> however, in all maven projects I tried ("mvn test"), the surefire plugin
> seems like passing a null reference instead of a Description instance that
> "describes the tests to be run "
> Note: other methods in the RunListener I tested seems fine (i.e., they get a
> valid Description object as input)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
