olamy commented on PR #3259: URL: https://github.com/apache/maven-surefire/pull/3259#issuecomment-3882267535
I'm a bit -0 on those providers warning as it will be look like running project with junit4 ``` [INFO] Using auto detected provider org.apache.maven.surefire.junit.JUnit3Provider [WARNING] JUnit4 provider is deprecated, will be removed in future versions of plugin ``` or with testNG ``` [INFO] Using auto detected provider org.apache.maven.surefire.testng.TestNGProvider [WARNING] TestNG provider is deprecated, will be removed in future versions of plugin. ``` Reading this most of the users who doesn't know anything about surefire architecture with providers will enter in some panic mode and think "Oh I will not be able to run anymore my junit3/4 to TestNG tests" We are refining the internal Surefire architecture regarding providers, but for most users, this change is invisible. Many users aren't aware that Surefire automatically scans your project dependencies, sets up the test environment for you and add some provider. This behavior is not changing. whether you use JUnit 3/4 or TestNG, we will still automatically detect the framework and inject the correct provider (only one) and dependencies for users. The only breaking change: We are removing the legacy provider for POJO tests (tests that run without a framework). Unless you are running raw POJO tests, your build will (should :)) continue to pass with zero changes. -- 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]
