【Gradle教程】第一章：引言

We would like to introduce Gradle to you, a build system that we think is a quantum leap for build technology in the Java (JVM) world. Gradle provides:
<翻译>我们准备把Gradle介绍给你，我们认为它是一个在Java构建技术世界里具有巨大突破性的构建工具。Gradle具有如下特性：

1. A very flexible general purpose build tool like Ant.
   <翻译>一个像Ant一样灵活且通用的构建工具。
2. Switchable, build-by-convention frameworks a la Maven. But we never lock you in!
   <翻译>一种可切换的，像Maven一样的基于约定的构建框架，却又从不约束你（约定优于配置）。
3. Very powerful support for multi-project builds.
   <翻译>对多项目构建的强力支持。
4. Very powerful dependency management (based on Apache Ivy).
   <翻译>对依赖管理的强力支持（基于Apache Ivy）。
5. Full support for your existing Maven or Ivy repository infrastructure.
   <翻译>对已有的Maven和Ivy仓库有着全面的支持。
6. Support for transitive dependency management without the need for remote repositories or pom.xml and ivy.xml files.
   <翻译>支持可传递性的依赖管理，而不需要远程仓库或者pom.xml和ivy.xml配置文件。
7. Ant tasks and builds as first class citizens.
   <翻译>Gradle能够很好地支持Ant任务和构建 。（有更好的翻译欢迎提议）
8. Groovy build scripts.
   <翻译>支持用Groovy语言编写Gradle的脚本。
9. A rich domain model for describing your build.
   <翻译>拥有丰富的领域模型来构建你的脚本。

In Chapter 2, Overview you will find a detailed overview of Gradle. Otherwise, the tutorials are waiting, have fun :)
<翻译>在第二章《概述》中，你将会看到关于Gradle的详细概述。否则的话，请继续阅读教程(http://ask.android-studio.org/?/article/15)，祝你愉快:)

1.1. About this user guide 关于本用户指南

This user guide, like Gradle itself, is under very active development. Some parts of Gradle aren't documented as completely as they need to be. Some of the content presented won't be entirely clear or will assume that you know more about Gradle than you do. We need your help to improve this user guide. You can find out more about contributing to the documentation at the Gradle web site.
<翻译>这篇用户指南就像Gradle本身一样，正处于一个经常变动更新的状态。有些部分并没有想象中那么完善，有些内容并没有足够清晰的表达出来或者有些内容是建立在假设你已经对Gradle有一定了解的基础上（实际上你可能对Gradle并不是很了解）。我们需要你帮助完善这篇指南，你可以在Gradle的官方网站上找到更多有助于阅读该指南的文档。

Throughout the user guide, you will find some diagrams that represent dependency relationships between Gradle tasks. These use something analogous to the UML dependency notation, which renders an arrow from one task to the task that the first task depends on.
<翻译>贯穿整个用户指南，你会发现一些用于描绘Gradle tasks之间的依赖关系的图表。这些图表有点像UML的依赖标记一样，从一个task延伸出一个箭头指向另一个task，这表示前一个task依赖于后一个task。

原文地址：http://www.gradle.org/docs/cur ... .html
翻译者：Jerry
邮箱：hjpdyxhjd@163.com