Maven manually add JAR packages to the local repository

Maven is really a good thing to manage projects, but if you download the JAR remotely through Maven, the bandwidth of my dorm is 4 trillion,
4 people sharing, sometimes using Maven to remotely download the JAR package will appear very slow, generally I find the download speed is not obvious, I have Ctrl + C to terminate its download.
Then use manual to download, because the Thunderbolt a class of tools to download will be much faster. I have manually downloaded many JAR packages from Maven's local repository on my machine.
A manual download brings up the question of how to manually add the downloaded JAR package to Maven's local repository. There is also a lot of information on the Internet.
I'll say what I'm doing.
First of all
recommend a few good Maven common warehouse URLs:
http://mvnrepository.com/
http://search.maven.org/
http://repository.sonatype.org/content/groups/public/
http://people.apache.org/repo/m2-snapshot-repository/
http://people.apache.org/repo/m2-incubating-repository/

The first one is my most used, then the second, then the third, and the last two is the private Apache warehouse, I have not used, but it should be able to feel it ...
Next, it is a consistent style, the use of easy-to-understand way to explain:

If you have read my previous article:Spring Mail Service Html:maven + spring SMTP mail with HtmlArticle, inside need to use a
Spring-context-support-3.1.0.release.jar jar package, I put it into the local warehouse when the picture was cut down, by the way, write this article,
For the needs of netizens reference.
First, tohttp://mvnrepository.com/This web, in the search field to enter the JAR package you want to search for keywords to search, the following direct mapping:

@1 Chart


@2 Chart


@3 Chart

"Note: If the coordinates are fixed in the project, follow the actual project coordinates"

Take Spring-context-support-3.1.0.release.jar as an example, the groupid,artifactid,version information for this jar package has been given in the @3 diagram,
This information should not be changed when manually installed, otherwise the jar package download will fail if the Maven project is migrated. By the way, this information is posted below to facilitate comparison:

<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-context-support</artifactId>
<version>3.1.0.RELEASE</version>
</dependency>

The commands for Maven install JAR packages are:

MVN Install:install-file-dfile=jar The position of the package-dgroupid= above the groupid-dartifactid= above the artifactid-dversion= above the version- Dpackaging=jar

For example:
The jar package I downloaded was placed in the D:\MVN directory (D:\mvn\spring-context-support-3.1.0.RELEASE.jar)
So the command I typed in cmd would be:

MVN Install:install-file-dfile=d:\mvn\spring-context-support-3.1.0.release.jar-dgroupid=org.springframework- Dartifactid=spring-context-support-dversion=3.1.0.release-dpackaging=jar

Enter to display the installation success:

Maven manually add JAR packages to the local repository