[
https://issues.apache.org/jira/browse/SUREFIRE-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15710160#comment-15710160
]
ASF GitHub Bot commented on SUREFIRE-1306:
------------------------------------------
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/132
@britter
I have fixed the issue but it is JUnit 4.7 issue.
This is useless `.addGoal( "-Dprovider=surefire-junit4" )` and
`.setJUnitVersion( "4.7" )` ditto because it's always the same in every test.
WDYT?
> JUnit4RerunFailingTestsIT does not execute with the JUnit version configured
> in the test
> ----------------------------------------------------------------------------------------
>
> Key: SUREFIRE-1306
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1306
> Project: Maven Surefire
> Issue Type: Test
> Reporter: Benedikt Ritter
> Assignee: Tibor Digana
> Fix For: 2.19.2
>
>
> All the test methods in JUnit4RerunFailingTestsIT set JUnit Version
> explicitly to 4.7 by calling {{setJUnitVersion( "4.7" )}}. This will in turn
> set the system property {{junit.version}}. The problem with this is, that the
> pom.xml in the test project (junit4-rerun-failing-tests) uses the property
> {{junitVersion}} instead. The version is set to 4.4 in pom.xml. Furthermore
> using JUnit 4.7 version in pom.xml results in test failures.
> Suggested solution: Drop the {{junitVersion}} property from pom.xml and use
> {{junit.version}} instead, making it possible to set the version from the
> test cases. Use version 4.12, since there seems to be a regression in 4.7
> causing the test to fail with this version.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
