[MENFORCER-152] Add Rule: BanDuplicatePomDependencyVersions
See also MNG-5091: Add option to fail build if WARNING's appear in POM

git-svn-id: https://svn.apache.org/repos/asf/maven/enforcer/trunk@1488785 13f79535-47bb-0310-9956-ffa450edef68
[MENFORCER-152] Refactor code, there are more spots with dependencies

git-svn-id: https://svn.apache.org/repos/asf/maven/enforcer/trunk@1488792 13f79535-47bb-0310-9956-ffa450edef68
[MENFORCER-152] also check depManagement and profiles

git-svn-id: https://svn.apache.org/repos/asf/maven/enforcer/trunk@1488797 13f79535-47bb-0310-9956-ffa450edef68
[MENFORCER-153] prepare new folder structure

git-svn-id: https://svn.apache.org/repos/asf/maven/enforcer/trunk@1489140 13f79535-47bb-0310-9956-ffa450edef68
Move ITs to projects-folder, next to mrm-folder

git-svn-id: https://svn.apache.org/repos/asf/maven/enforcer/trunk@1489142 13f79535-47bb-0310-9956-ffa450edef68
[MENFORCER-153] adjust projectsDirectory

git-svn-id: https://svn.apache.org/repos/asf/maven/enforcer/trunk@1489148 13f79535-47bb-0310-9956-ffa450edef68
[MENFORCER-154] Update maven-dependency-tree to 2.1 to make it work with Maven-3.1+ 

git-svn-id: https://svn.apache.org/repos/asf/maven/enforcer/trunk@1489158 13f79535-47bb-0310-9956-ffa450edef68
[MENFORCER-15] Use Mock Repository Manager for ITs 

git-svn-id: https://svn.apache.org/repos/asf/maven/enforcer/trunk@1489173 13f79535-47bb-0310-9956-ffa450edef68
[MENFORCER-15] Use Mock Repository Manager for ITs 

git-svn-id: https://svn.apache.org/repos/asf/maven/enforcer/trunk@1489553 13f79535-47bb-0310-9956-ffa450edef68
[MENFORCER-15] Use Mock Repository Manager for ITs 

git-svn-id: https://svn.apache.org/repos/asf/maven/enforcer/trunk@1489575 13f79535-47bb-0310-9956-ffa450edef68
[MENFORCER-83] Banned dependencies should support regular expressions

git-svn-id: https://svn.apache.org/repos/asf/maven/enforcer/trunk@1489638 13f79535-47bb-0310-9956-ffa450edef68
[MENFORCER-74] The bannedDependencies rule should support classifier
[MENFORCER-75] The bannedDependencies rule should support scope condition 


 

git-svn-id: https://svn.apache.org/repos/asf/maven/enforcer/trunk@1489999 13f79535-47bb-0310-9956-ffa450edef68
[MENFORCER-122] Adding repository causes NPE during mvn install
Add IT, can't reproduce issue although found a potential NPE when Repository.getReleases() == null

git-svn-id: https://svn.apache.org/repos/asf/maven/enforcer/trunk@1490031 13f79535-47bb-0310-9956-ffa450edef68
[MENFORCER-148] Broken hyperlink on Enforcer plugin usage page 

git-svn-id: https://svn.apache.org/repos/asf/maven/enforcer/trunk@1490452 13f79535-47bb-0310-9956-ffa450edef68
[MENFORCER-123] BannedDependencies version number not taken into account 
Update docs

git-svn-id: https://svn.apache.org/repos/asf/maven/enforcer/trunk@1490464 13f79535-47bb-0310-9956-ffa450edef68
Apply generics

git-svn-id: https://svn.apache.org/repos/asf/maven/enforcer/trunk@1490742 13f79535-47bb-0310-9956-ffa450edef68
Skip for current Maven3.1 release, until tychoteam has fixed the plugin.
With every newer Maven-version this test should be active again, since it should test for regression

git-svn-id: https://svn.apache.org/repos/asf/maven/enforcer/trunk@1490987 13f79535-47bb-0310-9956-ffa450edef68
[MENFORCER-42] Maven-Enforcer-Plugin fails in multimodule project when artifacts not in repository 

git-svn-id: https://svn.apache.org/repos/asf/maven/enforcer/trunk@1490991 13f79535-47bb-0310-9956-ffa450edef68
[MENFORCER-153] Use Mock Repository Manager for ITs 

git-svn-id: https://svn.apache.org/repos/asf/maven/enforcer/trunk@1491020 13f79535-47bb-0310-9956-ffa450edef68
[MENFORCER-134] Require Upper Bound Dependencies and matching Snapshot Dependencies 

git-svn-id: https://svn.apache.org/repos/asf/maven/enforcer/trunk@1491049 13f79535-47bb-0310-9956-ffa450edef68