翻譯專案請關注Github上的地址：
https://github.com/msdx/gradledoc
本文翻譯所在分支：
https://github.com/msdx/gradledoc/tree/2.0 。
線上瀏覽地址：
http://gradledoc.qiniudn.com/2.0/userguide/userguide.html 。
另外，Android 手機使用者可通過我寫的一個程式瀏覽文件，帶快取功能的，目前0.6開發中版本相容 Android 2.3以上系統，專案地址如下：
https://github.com/msdx/gradle-doc-apk
翻譯不易，轉載請註明本文在CSDN部落格上的出處：

關於我對Gradle的翻譯，以Github上的專案及http://gradledoc.qiniudn.com 上的文件為準。如發現翻譯有誤的地方，將首先在以上兩個地方更新。因時間精力問題，部落格中發表的譯文基本不會同步修改。

第二十七章. Ear 外掛

Chapter 27. The Ear Plugin

Ear 外掛添加了對組裝 Web 應用程式 EAR 檔案的支援。它添加了一個預設的 EAR 歸檔任務。它不需要 Java 外掛，但是對於也使用了 Java 外掛的專案，它將禁用預設的 JAR 歸檔生成。 
The Ear plugin adds support for assembling web application EAR files. It adds a default EAR archive task. It doesn't require the Java plugin, but for projects that also use the Java plugin it disables the default JAR archive generation.

27.1. 用法

27.1. Usage

要使用 Ear 的外掛，請在構建指令碼中包含以下語句：
To use the Ear plugin, include in your build script:

示例 27.1. 使用 Ear 外掛 - Example 27.1. Using the Ear plugin

build.gradle

apply plugin: 'ear'

27.2. 任務

27.2. Tasks

Ear 外掛向專案添加了以下任務。
The Ear plugin adds the following tasks to the project.

表 27.1. Ear 外掛——任務 - Table 27.1. Ear plugin - tasks

Ear 外掛向基礎外掛所加入的任務添加了以下的依賴。
The Ear plugin adds the following dependencies to tasks added by the base plugin.

表 27.2. Ear 外掛——額外的任務依賴 - Table 27.2. Ear plugin - additional task dependencies

27.3. 專案佈局

27.3. Project layout

表 27.3. Ear 外掛——專案佈局 - Table 27.3. Ear plugin - project layout

27.4. 依賴管理

27.4. Dependency management

Ear 外掛添加了兩個依賴配置：deploy 和 earlib。所有在 deploy 配置中的依賴都放在 EAR 存檔的根目錄中，並且是不具有傳遞性的。所有在 earlib 配置中的依賴都放在 EAR 歸檔的 'lib' 目錄中，並且是具有傳遞性的。 
The Ear plugin adds two dependency configurations: deploy and earlib. All dependencies in the deploy configuration are placed in the root of the EAR archive, and are not transitive. All dependencies in the earlibconfiguration are placed in the 'lib' directory in the EAR archive and are transitive.

27.5. 約定屬性

27.5. Convention properties

表27.4. Ear 外掛 ——目錄屬性 - Table 27.4. Ear plugin - directory properties

這些屬性由一個 EarPluginConvention 公約物件提供。 
These properties are provided by a EarPluginConvention convention object.

27.6. Ear

27.6. Ear

Ear 任務的預設行為是把 src/main/application 的內容複製到檔案的根目錄下。如果你的 application 目錄沒有包含 META-INF/application.xml 部署描述符，那麼將會為你生成一個。 
The default behavior of the Ear task is to copy the content of src/main/application to the root of the archive. If your application directory doesn't contain a META-INF/application.xml deployment descriptor then one will be generated for you.

另請參閱 Ear。
Also have a look at Ear.

27.7. 自定義

27.7. Customizing

下面是最重要的自定義選項的一個示例： 
Here is an example with the most important customization options:

示例 27.2. ear 外掛的自定義 - Example 27.2. Customization of ear plugin

build.gradle

apply plugin: 'ear'
apply plugin: 'java'

repositories { mavenCentral() }

dependencies {
    //following dependencies will become the ear modules and placed in the ear root
    deploy project(':war')

    //following dependencies will become ear libs and placed in a dir configured via libDirName property
    earlib group: 'log4j', name: 'log4j', version: '1.2.15', ext: 'jar'
}

ear {
    appDirName 'src/main/app'  // use application metadata found in this folder
    libDirName 'APP-INF/lib'  // put dependency libraries into APP-INF/lib inside the generated EAR;
                                // also modify the generated deployment descriptor accordingly
    deploymentDescriptor {  // custom entries for application.xml:
//      fileName = "application.xml"  // same as the default value
//      version = "6"  // same as the default value
        applicationName = "customear"
        initializeInOrder = true
        displayName = "Custom Ear"  // defaults to project.name
        description = "My customized EAR for the Gradle documentation"  // defaults to project.description
//      libraryDirectory = "APP-INF/lib"  // not needed, because setting libDirName above did this for us
//      module("my.jar", "java")  // wouldn't deploy since my.jar isn't a deploy dependency
//      webModule("my.war", "/")  // wouldn't deploy since my.war isn't a deploy dependency
        securityRole "admin"
        securityRole "superadmin"
        withXml { provider -> // add a custom node to the XML
            provider.asNode().appendNode("data-source", "my/data/source")
        }
    }
}

你也可以使用 Ear 任務提供的自定義選項，如 from 和 metaInf。 
You can also use customization options that the Ear task provides, such as from and metaInf.

27.8. 使用自定義的描述符檔案

27.8. Using custom descriptor file

假設你已經有了 application.xml中 並且希望使用它而不是去配置 ear.deploymentDescriptor 程式碼段，那麼就要把 META-INF/application.xml 放在你原始檔夾中的正確位置（請參閱 appDirName 屬性）。這樣現有的檔案內容將被使用，而 ear.deploymentDescriptor 中的顯式配置則會被忽略。 
Let's say you already have the application.xml and want to use it instead of configuring the ear.deploymentDescriptor section. To accommodate that place the META-INF/application.xml in the right place inside your source folders (see the appDirName property). The existing file contents will be used and the explicit configuration in the ear.deploymentDescriptor will be ignored.