maven project into the jar package from a local to a local warehouse

Method One (recommended):

<dependency>
            <groupId>guagua-commons</groupId>
            <artifactId>guagua-commons</artifactId>
            <version>1.0.1</version>
            <scope>system</scope>
            <systemPath>${project.basedir}/lib/guagua-commons-1.0.1.jar</systemPath>
</dependency>

As above, the packet replication jar guagua-commons-1.0.1.jar to project root directory (directory src and similar) of lib folder, was added <scope> System </ scope>
<systemPath>} $ {project.basedir / lib / jar package name </ systemPath> to

method two:
into the bin in maven installation directory under the directory cmd, run: mvn install: install-file -Dfile = jar package path -DgroupId = <groupId> in contents -DartifactId = <artifactId> tag -Dversion = <version> -Dpackaging = jar contents appear BUILD sUCCESS i.e. successful, then normally introduced into jar package in the project.
　　Drawbacks: When the project with the exchange server, you need to re-operate the same jar package into the local maven repository.
Examples: mvn install: install-File DFILE = F: \ the Message \-DgroupId-Commons-DartifactId = = guagua guagua-Commons -Dversion = 1.0.1 -Dpackaging guagua = JAR-Commons-1.0.1.jar      appear BUILD SUCCESS That success;

After the project in the normal import jar package to:

<dependency>
            <groupId>guagua-commons</groupId>
            <artifactId>guagua-commons</artifactId>
            <version>1.0.1</version>
</dependency>