(v) MAVEN directory structure and common command description

Some of the knowledge mentioned earlier involves some of the commands that are commonly used in MAVEN's directory structure and MAVEN, where we give you a brief introduction.

1.Maven Directory Structure Description

The Maven overall directory structure is as follows:

Bin directory: This directory contains scripts run by MVN that are used to configure java commands , prepare classpath and related Java System Properties, and then execute the Java command.

Boot directory: This directory contains only one file, in maven3.0.4 as an example, and the file is Plexus-classworlds-2.4.jar. Plexus-classworlds is a class-plus

carrier frame, phase for the default Java ClassLoader, it provides a richer syntax for easy configuration, andMaven uses the framework to load its own class library. More about Classworlds

For information, please refer to http://classworlds.codehaus.org/ . For a Maven user, you don't have to care about the file.

conf Directory: This directory contains a very important file Settings.xml,maven the core configuration file .

lib directory: This directory contains all The Java class library required by the MAVEN runtime ,maven itself is a sub-module open , so users can see things like Mavn-core-3.0.4.jar,

Maven-model-3.0.4.jar files like that, It also contains some Maven uses third-party dependencies such as Common-cli-1.2.jar and so on.

2.Maven Common Command Description

mvn Clean: indicates that the cleanup operation is run ( the data in the target folder is cleaned by default).

mvn Clean Compile: indicates that running the compilation after running cleanup will compile the code into the target folder.

mvn clean test: run cleanup and testing.

mvn Clean Package: run cleanup and packaging.

mvn clean Install: running cleanup and installation will install the punched package into the local warehouse so that other items The target can be called.

mvn Clean Deploy: run cleanup and publish (publish to a).

Most of the above commands are ligatures and can be split and executed separately, which is alive, looking at people's preferences and usage requirements, and Eclipse Run as provides common commands to MAVEN projects.

3. Special Instructions

The MAVEN project management tools are often integrated in the subsequent Eclipse Ides since Maven3, so there's no specific way to say how to install them in eclipse

The Maven plugin, in a follow-up introduction, might mention some of how to configure our own Maven in Eclipse, which is a relatively simple piece of content that you can explore on your own.

I wish you all can master this easy-to-use Project management tool, if you like to focus on technology friends can also learn about other similar to the technology and framework, to give you a

A simple example: Gradle. As for Maven before the make, ant silly what, I think there is no need to learn, but also basically do not use, a reality, eat something

Most important.

(v) MAVEN directory structure and common command description