[MPLUGIN-522] The auto prerequisites are way too aggressive

**[Tamas Cservenak](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cstamas)** opened **[MPLUGIN-522](https://issues.apache.org/jira/browse/MPLUGIN-522?redirect=false)** and commented

IMHO the implementation done in MPLUGIN-425 and MPLUGIN-424 are wrong.

They are way too aggresive and violate backward compatibility: if new feature is not explicitly set by user, code should not "come up" with some automatic value. By having the value not set simply means user does not want to use it.

This is especially true for (maven or java) prerequisite, as it creates HARD BREAKAGE if not met. Use of prerequisite is opt-in, but now it is FORCED onto user.

[Konrad Windszus](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kwin) 

---

**Issue Links:**
- [MPLUGIN-523](https://issues.apache.org/jira/browse/MPLUGIN-523) Split Maven3 and Maven4 support
(_**"is blocked by"**_)
- [MNG-7566](https://issues.apache.org/jira/browse/MNG-7566) Allow a Maven plugin to require a Java version through its plugin descriptor
(_**"is caused by"**_)
- [MPLUGIN-425](https://issues.apache.org/jira/browse/MPLUGIN-425) Plugin descriptor should contain the requiredJavaVersion/requiredMavenVersion
(_**"is caused by"**_)

**Remote Links:**
- [GitHub Pull Request #282
](https://github.com/apache/maven-plugin-tools/pull/282)