@sg11pankaj But that's different log. The entire problem was that the old versions threw an `RuntimeException` inside of the provider, broke provider's functionality and the log went to the native stream which means you could not find the warning in console log but in dump file (target/surefire-reports). In my opinion it's good that you see the warning because the s/w is not able to read your mind and understand a problem or expected issue to happen. So it can be easily a problem and the developer like you should be informed about problem candidate. The class name may easily have typo or the class could be reallocated to another package without any notion about the existence in POM.
[ Full content available at: https://github.com/apache/maven-surefire/pull/177 ] This message was relayed via gitbox.apache.org for [email protected]
