Today, MAVEN does some tidying up, better thinking:
This blog post is still very detailed:
Http://www.cnblogs.com/haippy/archive/2012/07/04/2576453.html
About Springboot's pit:
https://my.oschina.net/tridays/blog/825245
1. General Maven Project:
Https://jingyan.baidu.com/album/f25ef254a829a6482c1b8224.html?picindex=8
Using the method above to package the project into a jar and then into the form of a MAVEN jar into the local repository, we can introduce it in another project.
In fact, a total of two steps:
(1) To target the item to a JAR file:
Step Two:
Step three: Convert the jar package into Maven form:
This is under the cmd command:
This is also done in Springboot, where each module is made into a jar according to the above steps, and then referenced in the POM.
About MVN clean and mvn install:
http://blog.csdn.net/abc86319253/article/details/44019881
The above approach is to use the package method, you need to use mvn install in CMD to add to the local repository.
Use Spring-boot-maven-plugin to install jar to local repository in Springboot:
Https://www.jianshu.com/p/bcf627a409f2
http://blog.csdn.net/Colton_Null/article/details/77510141
Maven commands: The difference between install, package, clean:
Clean: Clears the compiled directory, which is the target directory by default and clears the files under the target directory.
Specific:
The MAVEN build is equivalent to the MAVEN command:
Indicates that the MAVEN project is packaged.
Maven Clean is equivalent to the MAVEN command:
Represents the removal of content under the target directory of the MAVEN project.
Maven install equals the command:
Indicates that the jar package is published to the local Maven repository.
Executing the MVN compile command generates a target file in the root directory.
Ps:maven is a very good tool, the above is just the most commonly used in a few commands, more specific can refer to a good book, "Maven combat."
About the MAVEN project hit jar problem