Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.4.3
-
Fix Version/s: 2.7.2
-
Component/s: Junit 4.x support
-
Labels:None
-
Environment:$ mvn --version
Maven version: 2.0.9
Java version: 1.6.0_07
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
-
Complexity:Intermediate
-
Testcase included:yes
-
Number of attachments :
Description
Have a dependency to junit-dep version 4.4 or later and a transitive or optional dependency to junit-3.8.1 and suddenly the fix for SUREFIRE-378 has been deceived. Your JUnit4 tests will again be executed as if they were POJO-tests.
The attached maven-project reveals the bug.
Attachments
Issue Links
| This issue supercedes: | ||||
| SUREFIRE-378 | junit-dep 4.4 isn't detected; tests are treated as POJO tests. |
|
|
|
Activity
Hide
Antony Stubbs
added a comment -
Fascinating. I just bumped into this issue as well. Looks like there's a unit test missing from the junit test suite eh? This is definitely a regression.
Is there a work around for this? For now, I'll switch back to junit (with out the -dep 
)
Show
Antony Stubbs
added a comment - Fascinating. I just bumped into this issue as well. Looks like there's a unit test missing from the junit test suite eh? This is definitely a regression.
Is there a work around for this? For now, I'll switch back to junit (with out the -dep )
)
The uploaded patch "surefire519-fix-and-test.patch" fixes the issue by specifying "junit:junit-dep" as the default JUnit artifact.
Backward compatibility is preserved by having the
SUREFIRE-378fix reversed. I.e. check for the alternate artifact name "junit:junit" in case the default was not found ...SUREFIRE-378fix reversed. I.e. check for the alternate artifact name "junit:junit" in case the default was not found ...