[
http://jira.codehaus.org/browse/SUREFIRE-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henrik Kaipe updated SUREFIRE-519:
----------------------------------
Attachment: surefire519-fix-and-test.patch
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-378 fix reversed.
I.e. check for the alternate artifact name "junit:junit" in case the default
was not found ...
> junit-dep 4.4+ isn't detected - transitive dependency to JUnit-3.x causes
> POJO-test treatment
> ---------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-519
> URL: http://jira.codehaus.org/browse/SUREFIRE-519
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support
> Affects Versions: 2.4.3
> 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"
> Reporter: Henrik Kaipe
> Attachments: junitdep45-and-transitive-junit3-dependency.zip,
> surefire519-fix-and-test.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
