1, maven of two core:
** dependency management: to jar package management process
** Project Builder: Project After encoding is complete, the project to compile, test, package, a series of operational deployment through the command to achieve
2, maven project life cycle
In maven existence of "three" life cycle, each set of life-cycle independent of each other. In a life cycle, the latter operation is automatically performed before the command execution
CleanLifeCycle : clean up the life cycle
Clean: After emptying compiled class files
defaultLifeCycle : default life cycle
compile,test,package,install,deploy
Which Package: packaged into the root of the target directory in which
The Install : package to a local warehouse
Deploy: The jar to deploy the package PW
siteLifeCycle : Site Life Cycle
3, depending on the range of
Add Dependency Range: default compile
Provided: Run to deploy to tomcat is not required
If the servlet-api.jar to compile, after the package contains serlvet-api.jar , the WAR package deploy to tomcat with tomcat exists servlet-api.jar package conflicts. Lead to fail.
4, transmission range-dependent (jar all packages are not passed down infinite)
A: ssh-service engineering
B: ssh-dao engineering
C: junit unit test
Summary: When the project one of its dependencies need not passed over. Add the corresponding rely on their own projects can be.
Should not necessarily rely on previous modifications are again, in their own modules can be added directly to come.
5, Pom.xml: Project Object Model
Coordinate information a) the project
b) The project jdk compiled version information
Coordinate information c) dependencies needed by the project
