[
https://jira.codehaus.org/browse/SUREFIRE-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318427#comment-318427
]
Henning Gross commented on SUREFIRE-952:
----------------------------------------
Hi! I am sorry. I got confused while putting together the example. Of course I
wanted to do that with 2.13 not 2.3. That may also be the reason why I couldnt
reproduce the issue. Your information solves all my confusion:
"Surefire will ignore that only if no "target/test-classes" directory was
created by the build"
I am not sure and will not be able to check soon but this could be the reason
why sometimes it would fail and in other modules not. I am really sorry for all
the confusion but I just could not get it together. I has some example project
and a real-life multi-module-project and simply did not get the behaviour. I
dont know if that explains everything but I would suggest we close this issue
and if I really come across a bug i can reproduce I will open a new issue w/o
all this confusion.
Regards!
> 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
> Attachments: surefire-952.zip
>
>
> 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
