maven occur, the maven inheritance model must be pinned against a particular
  modelVersion. This is required so that a change from modelVersion 4.0.0 to
  4.1.0 doesn't cause compatibility problems with users who have not upgraded
  their projects. It also allows for a certain amount of legacy support into the
  future. Therefore, we should rename this file from pom.xml in the maven-core

    pragmatic software license, and a desire to create high quality software that leads the way in its field.
    We consider ourselves not simply a group of projects sharing a server, but rather a community of developers
    and users.
  </description>
  <licenses>
    <license>
      <name>The Apache Software License, Version 2.0</name>
      <url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
      <distribution>repo</distribution>

    pragmatic software license, and a desire to create high quality software that leads the way in its field.
    We consider ourselves not simply a group of projects sharing a server, but rather a community of developers
    and users.
  </description>
  <licenses>
    <license>
      <name>The Apache Software License, Version 2.0</name>
      <url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
      <distribution>repo</distribution>

  </ciManagement>
  <mailingLists>
    <mailingList>
      <name>Maven User List</name>
      <subscribe>users******@****.***</subscribe>
      <unsubscribe>users******@****.***</unsubscribe>
      <post>users@maven.apache.org</post>
      <archive>http://mail-archives.apache.org/mod_mbox/maven-users</archive>
    </mailingList>
    <mailingList>
      <name>Maven Developer List</name>

                new ManagedDependencyContextRefiner(getScopeManager()));
    }

    /**
     * This method produces "surrogate" type registry that is static: it aims users that want to use
     * Maven-Resolver without involving Maven Core and related things.
     * <p>
     * This type registry is NOT used by Maven Core: Maven replaces it during Session creation with a type registry

  <mailingLists>
    <mailingList>
      <name>Maven Wagon User List</name>
      <subscribe>wagon-users******@****.***</subscribe>
      <unsubscribe>wagon-users******@****.***</unsubscribe>
      <archive>http://mail-archives.apache.org/mod_mbox/maven-wagon-users/</archive>
    </mailingList>
    <mailingList>
      <name>Maven Wagon Developer List</name>

  <mailingLists>
    <mailingList>
      <name>Maven Wagon User List</name>
      <subscribe>wagon-users******@****.***</subscribe>
      <unsubscribe>wagon-users******@****.***</unsubscribe>
      <archive>http://mail-archives.apache.org/mod_mbox/maven-wagon-users/</archive>
    </mailingList>
    <mailingList>
      <name>Maven Wagon Developer List</name>

Documentation
-------------

More information can be found on [Apache Maven Homepage][maven-home].
Questions related to the usage of Maven should be posted on
the [Maven User List][users-list].


Where can I get the latest release?
-----------------------------------
You can download the release source from our [download page][maven-download].

Contributing
------------

 |
 |                 -t /path/to/user/toolchains.xml
 |
 |  2. Global Level. This toolchains.xml file provides configuration for all Maven
 |                 users on a machine (assuming they're all using the same Maven
 |                 installation). It's normally provided in
 |                 ${maven.conf}/toolchains.xml.
 |

    pragmatic software license, and a desire to create high quality software that leads the way in its field.
    We consider ourselves not simply a group of projects sharing a server, but rather a community of developers
    and users.
  </description>
  <licenses>
    <license>
      <name>The Apache Software License, Version 2.0</name>
      <url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
      <distribution>repo</distribution>