[MENFORCER-241] DependencyConverge - allow ignoring minor and patch level mismatches

**[Stefan Fussenegger](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=sfussenegger)** opened **[MENFORCER-241](https://issues.apache.org/jira/browse/MENFORCER-241?redirect=false)** and commented

sometimes it is acceptable to allow some degree of version mismatches. For instance, if an artifact follows [semantic versioning rules](http://semver.org/) it is acceptable to allow patch level mismatches (bug fixes) or even minor level mismatches (added backward compatible functionality).

This new feature could somehow replace the current `uniqueVersions` flag which pretty much does the same thing to a lesser degree

---

**Affects:** 1.4.1

**Attachments:**
- [MENFORCER-241.patch](https://issues.apache.org/jira/secure/attachment/12766318/MENFORCER-241.patch) (_4.40 kB_)

**Issue Links:**
- [MENFORCER-360](https://issues.apache.org/jira/browse/MENFORCER-360) requireUpperBoundDeps should have option to check for same major version
(_**"is duplicated by"**_)
- [MENFORCER-360](https://issues.apache.org/jira/browse/MENFORCER-360) requireUpperBoundDeps should have option to check for same major version

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

Start by reviewing the linked GitHub Pull Request #16 and the attached MENFORCER-241.patch, then compare the proposed behavior with the current uniqueVersions flag. Done means the requested handling of minor and patch-level version mismatches is implemented and the related dependency-convergence behavior is covered by the project’s tests.

Written by the indexing model from the issue text.