You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Plugin validation warnings change: they are not littered in console log anymore, but are collected and reported at the build end. Moreover, the validation checks have been extended, more warnings are to be expected if build contains plugins that may not work with upcoming Maven 4. The build end validation report verbosity can be controlled by maven.plugin.validation property values “brief”, “default” and “verbose”. The validation report cannot be turned off, only by not having validation issues in the build, when the report is not shown. See MNG-7712, MNG-7754 and MNG-7767. Almost all of the ASF Maven plugins have been released with fixes to get rid of warnings, updating them is recommended. See Available Plugins page for current plugin versions. For non-ASF plugins, contact plugin maintainers to apply required changes.
The text was updated successfully, but these errors were encountered:
THIS IS A BUG TRACKER ONLY. FOR QUESTIONS PLEASE CHECK FAQ OR USE FORUM:
http://www.jacoco.org/jacoco/trunk/doc/faq.html
https://groups.google.com/forum/?fromgroups=#!forum/jacoco
Please understand that
ISSUES WITHOUT FOLLOWING INFORMATION WILL BE CLOSED WITHOUT COMMENTS!
Thank you for filling feature request!
Scenario
Current Behaviour
when running project using the current version of the above maven-plugin maven 3.9.2 gives a plugin validation error like this:
Wanted Behaviour
make plugin compatible to remove warning
Possible Workarounds
More info (taken from https://maven.apache.org/docs/3.9.2/release-notes.html )
The text was updated successfully, but these errors were encountered: