[MNG-7808] Remove warnings of undefined plugin versions

**[Benjamin Marwell](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mampf86)** opened **[MNG-7808](https://issues.apache.org/jira/browse/MNG-7808?redirect=false)** and commented

## Actual behaviour

Maven issues warnings about undefined plugin versions when not needed

## Expected behaviour

Maven should not issue warnings about undefined plugin versions early in a project build.

 

## Rationale

The release plugin will be modified to reject releases of projects which are not defining all plugin versions: [MRELEASE-1130] Reject release of project containing undefined plugin versions - ASF JIRA (apache.org)

 

Once that is done, we can remove the warnings from core:

1.) There should be as few as possible warnings OOTB on new maven projects

2.) It is not really important for local builds to define plugin versions.

---

**Issue Links:**
- [MNG-7666](https://issues.apache.org/jira/browse/MNG-7666) Update default binding and lifecycle plugin versions
(_**"is blocked by"**_)
- [MNG-7790](https://issues.apache.org/jira/browse/MNG-7790) Update lifecycle plugins
(_**"is blocked by"**_)
- [MNG-7790](https://issues.apache.org/jira/browse/MNG-7790) Update lifecycle plugins

- [MNG-7807](https://issues.apache.org/jira/browse/MNG-7807) Update Super POM plugins

- [MRELEASE-1130](https://issues.apache.org/jira/browse/MRELEASE-1130) Reject release of project containing undefined plugin versions
(_**"requires"**_)

Start by reviewing the linked MNG-7666, MNG-7790, MNG-7807, and MRELEASE-1130 issues to understand the dependency order and the current warning behavior. Trace the Maven core path that emits undefined-plugin-version warnings; done means early local builds no longer warn unnecessarily while release validation remains covered by the release-plugin work.

Written by the indexing model from the issue text.