sormuras commented on PR #3179: URL: https://github.com/apache/maven-surefire/pull/3179#issuecomment-3405030562
> What would the ramifications be for Surefire users that still use JUnit 3/4 tests if this change goes through & then later the JUnit folks decide to abruptly drop the JUnit Vintage engine in a future JUnit release? It's deprecated, but not for removal. Not slowly, not abruptly, not "everly". We think of it more as we do of JUnit 3 and 4: they are here to stay. Until the last user vanishes. So does the glue-code in `junit-vintage-engine`. As long as the JUnit Platform is supported by tools (including Maven), you get all the integration with your testing framework of choice. Through an implementation of a test engine. And in case of JUnit 3 and 4, both projects are in an end-of-life status, no change is to be expected on their side. Not discussed with the team, yet, but I could think of moving the [junit-vintage-engine](https://github.com/junit-team/junit-framework/tree/main/junit-vintage-engine) module as sibling right next to the [testng-engine](https://github.com/junit-team/testng-engine) project, making it a standalone top-level project. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
