sormuras commented on PR #3179: URL: https://github.com/apache/maven-surefire/pull/3179#issuecomment-3403686733
> The JUnit5 had one tendency 6 years ago, it was removal of Surefire and acceptance of "their" plugin. I know it because we talked about it that time. I assume you mean the "JUnit5 team"; the people behind the project. Right? If yes, we had "that time" and still have today more than "one tendency". We provided and still provide help, options, and alternatives for many tool authors and vendors to adopt to the (then new) JUnit Platform. Nothing changed there, we still do it happily and will do so in the foreseeable future. Are you mixing up the [junit-platform-surefire-provider](https://github.com/junit-team/junit-framework/tree/releases/5.0.x/junit-platform-surefire-provider) provided by the team (to support Surefire!) and my [junit-platform-maven-plugin](https://github.com/sormuras/junit-platform-maven-plugin) which was attempt to create Maven plugin talking directly to the JUnit Platform and playing nice with Java modules? > I saw people who remove something because they think that the old must go away but it happens because they are maybe corrupted or they do not want to understand, they do not listen and nothing exists for them only their ambition. "corrupted"? The prefixed "maybe" doesn't make it sound any better. _While all participants should adhere to this code of conduct, we recognize that sometimes people may have a bad day, or be unaware of some of the code's guidelines. When that happens, you may reply to them and point out this code of conduct._ https://www.apache.org/foundation/policies/conduct -- 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]
