Repository: maven
Updated Branches:
refs/heads/master 7b26f757a -> fb6b2c690
[MNG-5967] Dependency updates.
Project: http://git-wip-us.apache.org/repos/asf/maven/repo
Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/fb6b2c69
Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/f
Repository: maven
Updated Branches:
refs/heads/master 45327208f -> 7b26f757a
[MNG-5967] Dependency updates.
Project: http://git-wip-us.apache.org/repos/asf/maven/repo
Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/7b26f757
Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/7
Repository: maven
Updated Branches:
refs/heads/master 2313861df -> 45327208f
[MNG-5971] Imported dependencies should be available to inheritance processing
o Updated to add various comments regarding the issue.
Project: http://git-wip-us.apache.org/repos/asf/maven/repo
Commit: http://git-wip
Repository: maven
Updated Branches:
refs/heads/master 5f726e25e -> 2313861df
[MNG-5971] Imported dependencies should be available to inheritance processing
o Updated to remove the 'include' scope. Everyone agrees to the 'import' scope
being broken the way it got implemented in Maven 2.0.x an