[ 
https://jira.codehaus.org/browse/SUREFIRE-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318323#comment-318323
 ] 

Henning Gross commented on SUREFIRE-952:
----------------------------------------

18:59:36 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to 
execute goal org.apache.maven.plugins:maven-surefire-plugin:2.13:test 
(default-test) on project tds-util-lib: groups/excludedGroups require TestNG or 
JUnit48+ on project test classpath

Happened to me in a module that does not have any tests and therefore does not 
include junit. The check should not be performed when there are not test 
classes at all, dont you think? I now need to include the dependency in every 
module in my multi-module-project.
                
> Incompatibility with future release 4.12 of junit (Categories)
> --------------------------------------------------------------
>
>                 Key: SUREFIRE-952
>                 URL: https://jira.codehaus.org/browse/SUREFIRE-952
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Junit 4.x support
>    Affects Versions: 2.12.2, 2.12.4
>            Reporter: Henning Gross
>            Priority: Blocker
>
> Junit is introducing some interesting new features on Categories in 4.12. 
> @Category will become @Inherited and @ExcludeCategory/@IncludeCategory will 
> accept a class-array instead of just a single class. As we need these 
> urgently we are currently testing with the current snapshot of junit 
> (https://oss.sonatype.org/content/repositories/snapshots/junit/junit/4.12-SNAPSHOT/).
>  Unfortuneately the version seems to be incompatible.
> All tests are executed always. Regardless of the settings in <groups> or 
> <excludedgroups>. Using 4.11 works fine. I do not know why this happens and 
> therefore cannot provide a patch but I would love to see it fixed. If someone 
> points me at the cause I will happily find a solution.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to