Plugin validation issues were detected in plugin(s)

After executing mvn clean verify everything compiles properly with success, but also I get the following:

[WARNING] Plugin validation issues were detected in 7 plugin(s)
[WARNING] 
[WARNING]  * org.apache.maven.plugins:maven-resources-plugin:3.2.0
[WARNING]  * org.apache.maven.plugins:maven-jar-plugin:3.2.2
[WARNING]  * org.jacoco:jacoco-maven-plugin:0.8.8
[WARNING]  * org.apache.maven.plugins:maven-compiler-plugin:3.10.1
[WARNING]  * org.codehaus.mojo:build-helper-maven-plugin:3.3.0
[WARNING]  * org.apache.maven.plugins:maven-surefire-plugin:2.22.2
[WARNING]  * com.mysema.maven:apt-maven-plugin:1.1.3
[WARNING] 
[WARNING] For more or less details, use 'maven.plugin.validation' property with one of the values (case insensitive): [BRIEF, DEFAULT, VERBOSE]

Firstly, I don't understand the warning itself, its affection on my code, etc.
Then how to fix that? And lastly, how to use maven.plugin.validaiton property? I couldn't find any docs about this.

It's a new feature to warn you that some plugin you are using may not work in future. You can make a lot quieter by using the brief mode, though it never goes away completely.

mvn package -Dmaven.plugin.validation=brief

You can set this in the MAVEN_ARGS environment variable and have it picked up everywhere, so apart from a warning "some plugins are out of date" you aren't distracted

export MAVEN_ARGS="-Dmaven.plugin.validation=brief"

tl;dr - Try Upgrading Maven. Worked for me.

I was getting these two Warnings ...

[WARNING]  * org.apache.maven.plugins:maven-compiler-plugin:3.10.1
[WARNING]  * org.apache.maven.plugins:maven-resources-plugin:3.2.0

... and I did not have either plugin configured in my POM. So I assumed that my installation of Maven was using older versions of those plugins automatically; I confirmed at Maven Central that both plugins had newer versions than the above; and I upgraded Maven from 3.9.2 -> 3.9.3. Now I get no warnings, even though my POM is unchanged.

Introduced in maven 3.9.x the maven validator shows you plugins that are not maven 4.x compatible. As long as you stay below maven 4.x there will be no impact to your build.

There are two types of reported plugins

Internal

• using deprecated plugins goals
• using deprecated plugins parameters
• using read only plugins parameters

-> users can fix their project by fixing configuration by editing their POMs. Users should consult actual plugin documentation or try to update plugin to newer version.

External

• using old, deprecated Maven Api by plugin
• declaring dependencies for Maven Core artifacts in wrong scope in plugin project

-> only fixable by maintainer

Remove message

To remove the message all together you can set locally

mvn -Dmaven.plugin.validation=none

> Can be added to MAVEN_OPTS or MAVEN_ARGS environment variables, can
> also be added to .mvn/maven.config file in order to configure per
> project.
>
> Users can add such property to their settings.xml file to change
> configuration globally.
>
> NOTICE as maven.plugin.validation is configuration item for Maven
> itself, it can not be used in project pom.xml

Other case insensitive options are as listed in the maven validator documentation:

• NONE - mute Plugin Validation completely, nothing will be reported
• INLINE - report only Internal issues in place where occur
• BRIEF - report only Internal issues in place where occur and list of plugins
  with External issues at the and of build
• SUMMARY - report list of
  plugins with Internal and External issues at the end of build
• VERBOSE - report Internal and External issues at the end of build in verbose mode

I updated my Java version from 8 to 17. Worked for reasons i dont know