[
https://jira.codehaus.org/browse/SUREFIRE-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326285#comment-326285
]
Kristian Rosenvold commented on SUREFIRE-1000:
----------------------------------------------
This is a bigger issue than it seems, since the includes/excludes pattern
actually controls classloading. In its current shape, classes that dont match
the pattern aren't classloaded. Changing this will load all classes, which may
introduce failures in peoples build.
Some projects also make @Test annotated classes that they don't want to be run
by surefire.
While I am not /against/ this issue as such, it is a kind of "version 3.0"
change. Lots of builds will break if we do this.
> Support for Junit4 @Test annotation
> -----------------------------------
>
> Key: SUREFIRE-1000
> URL: https://jira.codehaus.org/browse/SUREFIRE-1000
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support
> Environment: All
> Reporter: Martin Spamer
>
> Should provide automation support for running test annotated with Junit4
> @Test. without need to defined paths (in compliance with Maven Convention or
> Configuration policy).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
