<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>

    <parent> <!-- 指定該pom的父級pom  -->
        <groupId>org.codehaus.mojo</groupId> <!-- 父級pom組織id -->
        <artifactId>my-parent</artifactId>  <!-- 父級pom標識 -->
        <version>2.0</version>  <!-- 父級pom版本 -->
        <relativePath>../my-parent</relativePath>   <!-- 父級pom位置 -->
    </parent>

    <groupId>com.yourcompany.app</groupId>  <!-- 當前專案的組織id -->
    <artifactId>app</artifactId>  <!-- 當前maven專案的唯一標識-->
    <version>1.0-SNAPSHOT</version>  <!-- 當前maven專案版本號 -->
    <packaging>pom</packaging>   <!-- 當前maven專案package 命令打包型別 eg.war、jar...-->
    <!-- 專案有多個模組時使用，解決專案之間的依賴關係。eg：web專案->框架專案 前臺專案 後臺專案... -->
    <modules>
        <module>webFrame</module>     <!-- 模組的名稱 -->
    </modules>

    <dependencies>              <!-- 管理專案依賴的jar包 -->
        <dependency>
            <groupId>junit</groupId>    <!-- 依賴的jar包組織名稱 -->
            <artifactId>junit</artifactId>  <!-- 依賴的jar包名稱-->
            <version>4.0</version>  <!-- 依賴的jar包版本號,寫法：
            1.0: "Soft" requirement on 1.0 (just a recommendation, if it matches all other ranges for the dependency)
            [1.0]: "Hard" requirement on 1.0
            (,1.0]: x <= 1.0
            [1.2,1.3]: 1.2 <= x <= 1.3
            [1.0,2.0): 1.0 <= x < 2.0
            [1.5,): x >= 1.5
            (,1.0],[1.2,): x <= 1.0 or x >= 1.2; multiple sets are comma-separated
            (,1.1),(1.1,): this excludes 1.1 (for example if it is known not to work in combination with this library)
            -->
            <type>jar</type> <!-- 依賴的jar包型別-->
            <scope>test</scope>  <!-- 依賴包使用區域 有：
            compile -> this is the default scope, used if none is specified. Compile dependencies are available in all classpaths. Furthermore, those dependencies are propagated to dependent projects.
            provided - this is much like compile, but indicates you expect the JDK or a container to provide it at runtime. It is only available on the compilation and test classpath, and is not transitive.
            runtime - this scope indicates that the dependency is not required for compilation, but is for execution. It is in the runtime and test classpaths, but not the compile classpath.
            test - this scope indicates that the dependency is not required for normal use of the application, and is only available for the test compilation and execution phases.
            system - this scope is similar to provided except that you have to provide the JAR which contains it explicitly. The artifact is always available and is not looked up in a repository.
            特別指明是system區域，管理本地的jar包，同時需要新增systemPath屬性來指明依賴包的位置-->
            <!--<systemPath>.../WEB-INF/lib/xxxxxx.jar</systemPath>-->
            <optional>true</optional>
            <exclusions>       <!-- 當依賴的這個包同時也依賴了其他包時，用來指明依賴該包所依賴的某一個包,不依賴該包所依賴的所有包使用*來匹配 -->
                <exclusion>
                    <groupId>org.apache.maven</groupId>
                    <artifactId>maven-core</artifactId>
                </exclusion>
                <!-- 依賴的jar包型別-->
            </exclusions>
        </dependency>
        <dependency>
            <groupId>org.apache.maven</groupId>
            <artifactId>maven-embedder</artifactId>
            <version>3.1.0</version>
            <exclusions>
                <exclusion>   <!-- 不依賴該包（org.apache.maven<）所依賴的所有包使 -->
                    <groupId>*</groupId>
                    <artifactId>*</artifactId>
                </exclusion>
            </exclusions>
        </dependency>
    </dependencies>
    <dependencyManagement>    <!-- 通常在父級pom中新增這個元素，用來管理一下共用的依賴，使得繼承該pom的子pom使用，子pom中是需要指定groupId 和 artifactId，版本號會自動被補全 -->
        <dependencies>
            <dependency>
                <groupId>org.apache.ant</groupId>
                <artifactId>ant</artifactId>
                <version>1.8.1</version>
            </dependency>
        </dependencies>
    </dependencyManagement>
    <!--
    properties->pom中的元素就一個pom的屬性，pom的頂級屬性就是project,屬性的訪問格式：${屬性名稱}，
    env.X: (訪問當前系統環境變數)Prefixing a variable with "env." will return the shell's environment variable. For example, ${env.PATH} contains the PATH environment variable.
Note: While environment variables themselves are case-insensitive on Windows, lookup of properties is case-sensitive. In other words, while the Windows shell returns the same value for %PATH% and %Path%, Maven distinguishes between ${env.PATH} and ${env.Path}. As of Maven 2.1.0, the names of environment variables are normalized to all upper-case for the sake of reliability.
    project.x:(訪問pom中的屬性<pom的元素>) A dot (.) notated path in the POM will contain the corresponding element's value. For example: <project><version>1.0</version></project> is accessible via ${project.version}.
    settings.x: (訪問配置檔案中的屬性)A dot (.) notated path in the settings.xml will contain the corresponding element's value. For example: <settings><offline>false</offline></settings> is accessible via ${settings.offline}.
Java System Properties: All properties accessible via java.lang.System.getProperties() are available as POM properties, such as ${java.home}.
    x: (訪問使用properties定義的變數)Set within a <properties /> element in the POM. The value of <properties><someVar>value</someVar></properies> may be used as ${someVar}.
    -->
    <properties>   <!-- 用來定義屬性 eg：定義了一個變數名為varName 值為varValue的屬性 訪問：${varName} -->
        <varName>varValue</varName>
    </properties>

    <!--
    repositories是一些附加在Maven倉庫目錄顯示的製品的集合，要想成為Maven倉庫的製品，pom檔案不需是$BASE_REPO/groupId/artifactId/version/artifactId-version.pom. $BASE_REPO結構
    repositories就是收集和儲存成品的地方。
    -->
    <repositories>
        <repository>   <!-- repository是Maven社群最有力的特性，預設的Maven倉庫中心是 http://repo.maven.apache.org/maven2/. -->
            <id>central</id>    <!-- 編譯配置 -->
            <name>Central Repository</name>    <!-- 編譯配置 -->
            <url>http://repo.maven.apache.org/maven2</url>    <!-- 編譯配置 -->
            <layout>default</layout>    <!-- 編譯配置 -->
            <snapshots>    <!-- 編譯配置 -->
                <enabled>false</enabled>    <!-- 編譯配置 -->
            </snapshots>
        </repository>
        <repository>
            <releases>
                <enabled>false</enabled>
                <updatePolicy>always</updatePolicy>
                <checksumPolicy>warn</checksumPolicy>
            </releases>
            <snapshots>
                <enabled>true</enabled>
                <updatePolicy>never</updatePolicy>
                <checksumPolicy>fail</checksumPolicy>
            </snapshots>
            <id>codehausSnapshots</id>
            <name>Codehaus Snapshots</name>
            <url>http://snapshots.maven.codehaus.org/maven2</url>
            <layout>default</layout>
        </repository>
    </repositories>
    <distributionManagement>        <!-- 成品釋出管理 -->

    </distributionManagement>
    <pluginRepositories>    <!-- 編譯配置 -->
        <pluginRepository>    <!-- 編譯配置 -->
            <id>central</id>    <!-- 編譯配置 -->
            <name>Central Repository</name>    <!-- 編譯配置 -->
            <url>http://repo.maven.apache.org/maven2</url>    <!-- 編譯配置 -->
            <layout>default</layout>    <!-- 編譯配置 -->
            <snapshots>    <!-- 編譯配置 -->
                <enabled>false</enabled>    <!-- 編譯配置 -->
            </snapshots>
            <releases>    <!-- 編譯配置 -->
                <updatePolicy>never</updatePolicy>    <!-- 編譯配置 -->
            </releases>
        </pluginRepository>
    </pluginRepositories>
    <!-- 編譯配置 -->
    <build>
        <defaultGoal>install</defaultGoal>      <!-- 設定預設的goal或phase 當什麼都沒有指定是執行該目標或階段-->
        <directory>${project.basedir}/target</directory>    <!-- 編譯後的檔案目標位置 路徑都是絕對路徑-->
        <outputDirectory>${project.build.directory}/classes</outputDirectory>     <!-- 編譯後的檔案輸出位置  -->
        <finalName>${project.artifactId}-${project.version}</finalName>    <!-- 編譯打包的檔名稱 -->
        <testOutputDirectory>${project.build.directory}/test-classes</testOutputDirectory>    <!-- 測試編譯後的檔案輸出位置  -->
        <sourceDirectory>${project.basedir}/src/main/java</sourceDirectory>    <!-- 需要編譯原始檔存放位置 -->
        <scriptSourceDirectory>src/main/scripts</scriptSourceDirectory>    <!-- 需要編譯指令碼原始檔存放位置 -->
        <testSourceDirectory>${project.basedir}/src/test/java</testSourceDirectory>    <!-- 編譯的測試原始檔存放位置  -->
        <resources>     <!-- 指定了工程的資源存放位置，這些資源不會被編譯但是她是捆綁在這個專案中的，如專案要求的配置檔案configuration.xml等，這些檔案需要在打包同時要打入包中 -->
            <resource>
                <directory>${project.basedir}/src/main/resources</directory>    <!-- 工程資源存放位置  -->
                <targetPath>META-INF/plexus</targetPath>    <!-- 打包後資源的位置 -->
                <filtering>false</filtering>
                <includes>         <!-- 指定需要打包的資源 -->
                    <include>configuration.xml</include>
                </includes>
                <excludes>    <!-- 指定不需要打包的資源 -->
                    <exclude>**/*.properties</exclude>
                </excludes>
            </resource>
        </resources>
        <!--
        resources:  is a list of resource elements that each describe what and where to include files associated with this project.
        targetPath: Specifies the directory structure to place the set of resources from a build. Target path defaults to the base directory. A commonly specified target path for resources that will be packaged in a JAR is META-INF.
        filtering:  is true or false, denoting if filtering is to be enabled for this resource. Note, that filter *.properties files do not have to be defined for filtering to occur - resources can also use properties that are by default defined in the POM (such as ${project.version}), passed into the command line using the "-D" flag (for example, "-Dname=value") or are explicitly defined by the properties element. Filter files were covered above.
        directory:  This element's value defines where the resources are to be found. The default directory for a build is ${basedir}/src/main/resources.
        includes:   A set of files patterns which specify the files to include as resources under that specified directory, using * as a wildcard.
        excludes:   The same structure as includes, but specifies which files to ignore. In conflicts between include and exclude, exclude wins.
        testResources: The testResources element block contains testResource elements. Their definitions are similar to resource elements, but are naturally used during test phases. The one difference is that the default (Super POM defined) test resource directory for a project is ${basedir}/src/test/resources. Test resources are not deployed.
        -->
        <testResources>
            <testResource>
                <directory>${project.basedir}/src/test/resources</directory>    <!-- 編譯配置 -->
            </testResource>
        </testResources>
        <filters>
            <filter>filters/filter1.properties</filter>
        </filters>
        <plugins>   <!-- 指定使用的外掛列表 -->
            <plugin>    <!-- 指定一個外掛  -->
                <artifactId>maven-antrun-plugin</artifactId>
                <version>1.1</version>
                <!--
                dependencies:   Dependencies are seen a lot within the POM, and are an element under all plugins element blocks. The dependencies have the same structure and function as under that base build. The major difference in this case is that instead of applying as dependencies of the project, they now apply as dependencies of the plugin that they are under. The power of this is to alter the dependency list of a plugin, perhaps by removing an unused runtime dependency via exclusions, or by altering the version of a required dpendency. See above under Dependencies for more information.
                executions:     It is important to keep in mind that a plugin may have multiple goals. Each goal may have a separate configuration, possibly even binding a plugin's goal to a different phase altogether. executions configure the execution of a plugin's goals.
                                For example, suppose you wanted to bind the antrun:run goal to the verify phase. We want the task to echo the build directory, as well as avoid passing on this configuration to its children (assuming it is a parent) by setting inherited to false. You would get an execution like this:
                id:             Self explanatory. It specifies this execution block between all of the others. When the phase is run, it will be shown in the form: [plugin:goal execution: id]. In the case of this example: [antrun:run execution: echodir]
                goals:          Like all pluralized POM elements, this contains a list of singular elements. In this case, a list of plugin goals which are being specified by this execution block.
                phase:          This is the phase that the list of goals will execute in. This is a very powerful option, allowing one to bind any goal to any phase in the build lifecycle, altering the default behavior of Maven.
                inherited:      Like the inherited element above, setting this false will supress Maven from passing this execution onto its children. This element is only meaningful to parent POMs.
                configuration:  Same as above, but confines the configuration to this specific list of goals, rather than all goals under the plugin.
-->
                <executions>
                    <execution>
                        <id>echodir</id>
                        <goals>
                            <goal>run</goal>
                        </goals>
                        <phase>verify</phase>
                        <inherited>false</inherited>
                        <configuration>
                            <tasks>
                                <echo>Build Dir: ${project.build.directory}</echo>
                            </tasks>
                        </configuration>
                    </execution>
                    <!-- 以上execution解讀： 繫結一個antrun:run的goal到verify階段，任務是輸出編譯的目錄，避免把這個配置傳到子pom中配置inherited為false -->
                </executions>
            </plugin>
        </plugins>

        <pluginManagement>  <!-- 外掛管理 -->
            <!-- NOTE: These plugins will be removed from future versions of the super POM -->
            <!-- They are kept for the moment as they are very unlikely to conflict with lifecycle mappings (MNG-4453) -->
            <plugins>
                <plugin>    <!-- 編譯配置 -->
                    <groupId>org.apache.maven.plugins</groupId>
                    <artifactId>maven-jar-plugin</artifactId>
                    <version>2.0</version>
                    <extensions>false</extensions>  <!-- 是否載入外掛的擴充套件，值：true|false 預設是false -->
                    <inherited>true</inherited> <!-- 這個外掛的configuration（配置）是否要施加到繼承該pom的子pom上 值：true|false 預設true -->
                    <configuration>   <!-- 對單個外掛指定配置，不需要深入瞭解這個外掛怎麼工作的，換句話說就是這個外掛期望的屬性都可以在這裡指定,
                    如果該pom是一個父級pom，這個配置也會被繼承，不管是在 build/plugins 還是在 pluginManagement中，如果子pom的外掛中設定了該configuration，
                      那麼子pom中的外掛配置值就是有效的，子pom中沒有設定，父級中配置了父級的就是有效的-->
                        <classifier>test</classifier> <!-- -->
                    </configuration>
                    <dependencies></dependencies>
                    <executions></executions>
                </plugin>
                <plugin>
                    <artifactId>maven-release-plugin</artifactId>
                    <version>2.0</version>
                </plugin>
            </plugins>
        </pluginManagement>
    </build>

    <reporting>    <!-- 包含了site階段相應地元素，maven會生成一個定義和配置在reporting元素下的報告，比如：JavaDoc報告，像build中配置外掛一樣的，reporting掌握了相同的能力
     明顯的不同是build中外掛的goal配置在executions塊中，reporting是配置在reportSet元素中,稍微的不同是reporting下的configuration扮演了build外掛的configuration
     相反則不然，也就是build外掛的配置（configuration）不會影響reporting外掛 -->
        <outputDirectory>${project.build.directory}/site</outputDirectory>    <!-- 文件輸出位置 -->
        <!-- 一個非常重要的是一個外掛有很多goal，每個goal可能有分開的配置（configuration），reportSets配置一個report外掛目標的執行，相同就是build的execution則不能繫結一個報告到其他階段 -->
        <plugins>
            <plugin>
                <artifactId>maven-project-info-reports-plugin</artifactId>
                <version>2.0.1</version>
                <reportSets>
                    <reportSet>
                        <id>sunlink</id>
                        <reports>
                            <report>javadoc</report>
                        </reports>
                        <inherited>true</inherited>
                        <configuration>
                            <links>
                                <link>http://java.sun.com/j2se/1.5.0/docs/api/</link>
                            </links>
                        </configuration>
                    </reportSet>
                    <!--
                    上述reportSet解讀：假如你想配置javadoc:javadoc這個goal來連線到http://java.sun.com/j2se/1.5.0/docs/api/，僅僅只是javadoc（不是maven-javadoc-plugin:jar目標）
                    同時想把這個配置傳遞給它的child，就設定inherited為true
                     -->
                </reportSets>
            </plugin>
        </plugins>
    </reporting>

    <profiles>
        <!-- NOTE: The release profile will be removed from future versions of the super POM -->
        <profile>
            <id>test</id>
            <activation>
                <activeByDefault>false</activeByDefault>
                <jdk>1.5</jdk>          <!-- jdk版本 -->
                <os>       <!-- 作業系統 -->
                    <name>Windows XP</name>
                    <family>Windows</family>
                    <arch>x86</arch>
                    <version>5.1.2600</version>
                </os>
                <property>
                    <name>sparrow-type</name>
                    <value>African</value>
                </property>
                <file>  <!-- 給定的檔案可能功能檔案的existence來啟用這個profile -->
                    <exists>${basedir}/file2.properties</exists>
                    <missing>${basedir}/file1.properties</missing>
                </file>
            </activation>
            <!-- 備註：activation元素不是profile被啟用的唯一方式，settings.xml檔案中的activeProfile元素可能包含了這個profile的id，通過命令工具它們也可能被啟用 -->
            <!--<build>...</build>-->
            <!--<modules>...</modules>-->
            <!--<repositories>...</repositories>-->
            <!--<pluginRepositories>...</pluginRepositories>-->
            <!--<dependencies>...</dependencies>-->
            <!--<reporting>...</reporting>-->
            <!--<dependencyManagement>...</dependencyManagement>-->
            <!--<distributionManagement>...</distributionManagement>-->
        </profile>
        <!--
        profile 4.0的一個新特性就是工程根據環境來改變設定，這個環境就是那裡將要被編譯。profile包含了可選的activation和對pom作出的該組變化，如果這個profile可以被啟用的話
        如：為測試環境編譯就可能需要指定一個不同的資料庫，然後釋出。或者依賴的包根據不同的jdk版本來從倉庫中獲取
        -->
        <profile>
            <id>release-profile</id>
            <activation>     <!-- activation是profile的關鍵，profile的能力就是根據確定的情況修改基礎的pom的能力，這些情形可以在activation元素中指定,一個和多個指定的標準被遇到是activation就會發生，但正數第一個被遇見時，處理停止並且這個profile被標記為啟用-->
                <property>    <!-- 編譯配置 -->
                    <name>performRelease</name>    <!-- 編譯配置 -->
                    <value>true</value>    <!-- 編譯配置 -->
                </property>
            </activation>

            <build>
                <plugins>
                    <plugin>
                        <inherited>true</inherited>
                        <artifactId>maven-source-plugin</artifactId>
                        <executions>
                            <execution>
                                <id>attach-sources</id>
                                <goals>
                                    <goal>jar</goal>
                                </goals>
                            </execution>
                        </executions>
                    </plugin>
                    <plugin>
                        <inherited>true</inherited>
                        <artifactId>maven-javadoc-plugin</artifactId>
                        <executions>
                            <execution>
                                <id>attach-javadocs</id>
                                <goals>
                                    <goal>jar</goal>
                                </goals>
                            </execution>
                        </executions>
                    </plugin>
                    <plugin>
                        <inherited>true</inherited>
                        <artifactId>maven-deploy-plugin</artifactId>
                        <configuration>
                            <updateReleaseInfo>true</updateReleaseInfo>
                        </configuration>
                    </plugin>
                </plugins>
            </build>
        </profile>
    </profiles>
</project>
 

資料參考：http://maven.apache.org/pom.html