[MNG-4173] Remove automatic version resolution for POM plugins

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

Maven 3.x will no longer try to automatically find the version for plugins specified in the POM, i.e. the effective POM must declare a version for each plugin used for the sake of reproducible builds. Omitting the plugin version will raise in error.

---

**Affects:** 3.0-alpha-3

**Issue Links:**
- [MNG-4205](https://issues.apache.org/jira/browse/MNG-4205) Remove support for plugin metaversions RELEASE and LATEST

- [MNG-3358](https://issues.apache.org/jira/browse/MNG-3358) Require explicit plugin versions
(_**"supercedes"**_)

**Remote Links:**
- [Page
](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65875544)

3 votes, 8 watchers

Start by reviewing the Maven core implementation and the superseding issue MNG-3358, which explicitly covers requiring plugin versions. Confirm how omitted plugin versions are currently resolved and identify the existing validation or error path; done means POM plugins without explicit versions no longer resolve automatically and instead produce an error.

Written by the indexing model from the issue text.