[
https://issues.apache.org/jira/browse/MNG-7986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799379#comment-17799379
]
Michael Osipov commented on MNG-7986:
-------------------------------------
What about Surefire 3.2.3? Don't expect anyone analyze several years old
releases...
> Spurious JUnit 4.12 jar on boot classpath
> -----------------------------------------
>
> Key: MNG-7986
> URL: https://issues.apache.org/jira/browse/MNG-7986
> Project: Maven
> Issue Type: Bug
> Components: Core
> Affects Versions: 4.0.0-alpha-9
> Reporter: Jean Gauthier
> Priority: Major
> Attachments: output-maven-4.0.0-alpha8-surefire-2.22.2.txt,
> output-maven-4.0.0-alpha9-surefire-2.22.2.txt,
> output-maven-4.0.0-alpha9-surefire-3.0.0-M4.txt, reproducer.zip
>
>
> We noticed a regression in Maven 4.0.0-alpha9 for Surefire versions
> 2.21.0-3.0.0-M3: when specifying a dependency to JUnit 4.13, JUnit 4.12 gets
> added before it on the boot classpath.
> This causes issues e.g. when defining a custom JUnit 4 RunListener in a
> project: because JUnit 4.12 is listed first, the new {{testSuiteStarted}}
> callback that was added in 4.13 does not get invoked anymore.
> This can be reproduced by running {{./mvnw clean test
> -Dorg.slf4j.simpleLogger.log.org.apache.maven.plugin.surefire.SurefirePlugin=debug}}
> on the attached project (and setting the Maven/Surefire versions
> accordingly).
> I have also added the output logs for the following version combinations as
> attachment to the ticket:
> * Maven 4.0.0-alpha8 + Surefire 2.22.2 => works correctly (contains
> {{RunListener - testSuiteStarted}})
> * Maven 4.0.0-alpha9 + Surefire 2.22.2 => broken (does not contain
> {{RunListener - testSuiteStarted}})
> * Maven 4.0.0-alpha9 + Surefire 3.0.0-M4 => works correctly (contains
> {{RunListener - testSuiteStarted}})
> Please let me know in case additional information is needed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
