Gradle进阶教程：超越基础

需积分: 9 101 浏览量更新于2024-07-22 收藏 9.56MB PDF 举报

"Gradle Beyond the Basics" 是一本由 Tim Berglund 编写的关于 Gradle 的高级指南，该书深入探讨了Gradle 这一强大的构建工具在软件开发中的实际应用和高级特性。这本书是 2013 年由 Gradle, Inc. 出版的，版权受到保护，特别强调了在美国的印刷发行以及 O'Reilly Media 的出版支持。它适用于教育、商业或销售推广用途，电子版也广泛提供。作者 Tim Berglund以其专业知识，带领读者超越基础概念，涵盖了诸如构建系统的工作原理、项目结构管理、依赖管理和插件体系的高级用法。书中可能包括模块化构建、多项目协作、持续集成/持续部署(CI/CD)的最佳实践，以及如何利用 Gradle 变量、任务定制和配置文件来提升构建效率。编辑 Mike Loukides 和 Meghan Blanchette 负责本书的质量把控，而 Production Editor Kara Ebrahim 和 Proofreader 同样对内容进行了严谨的校对。封面设计由 Randy Comer 完成，内部设计则由 David Futato 执行，插图由 Rebecca Demarest 添加视觉元素，确保了书籍的专业性和易读性。该书的第一版于 2013 年 7 月发布，随后可能进行了多次修订以保持内容的时效性和准确性。对于读者来说，可以通过访问 O'Reilly 官网获取最新版本的错误修正信息，网址为 <http://oreilly.com/catalog/errata.csp?isbn=9781449304676>。 "Gradle Beyond the Basics" 是一本理想的资源，不仅适合现有 Gradle 用户寻求深化理解的进阶教程，也适合那些希望进入现代构建工具领域并了解其高级特性的开发者。通过阅读这本书，开发者可以提升项目构建的灵活性、自动化和性能，从而提高软件开发的效率和质量。

from('config') {

exclude 'Development*.groovy'

}

into 'build/resources'

}

Transforming Directory Structure

The outcome of Example 1-4 is to put all source files into one flat directory, build/

resources. Of course you may not want to flatten all of the source directories; you might

instead want to preserve some of the structure of the source directory trees or even map

the source directories onto a new tree. To do this, we can simply add additional calls to

into inside the from configuration closures. This is shown in Example 1-5.

Example 1-5. A copy task mapping source directory structure onto a new destination

structure

task complexCopy(type: Copy) {

from('src/main/templates') {

include '**/*.gtpl'

into 'templates'

}

from('i18n')

from('config') {

exclude 'Development*.groovy'

into 'config'

}

into 'build/resources'

}

Note that a top-level call to into is still required—the build file will not run without it

—and the nested calls to into are all relative to the path of that top-level configuration.

If the number of files or the size of the files being copied is large, then a copy task could

be an expensive build operation at execution time. Gradle’s incremental build feature

helps reduce the force of this problem. Gradle will automatically incur the full execution

time burden on the first run of the build, but will keep subsequent build times down

when redundant copying is not necessary.

Renaming Files During Copy

If your build has to copy files around, there’s a good chance it will have to rename files

in the process. Filenames might need to be tagged to indicate a deployment environ‐

ment, or might need to be renamed to some standard form from an environment-

specific origin, or might be renamed according to a product configuration specified by

the build. Whatever the reason, Gradle gives you two flexible ways to get the job done:

regular expressions and Groovy closures.

Copy Task | 3

www.it-ebooks.info

working directory into the build directory, it would be convenient to replace the

deploymen

t-variable strings as a part of the copy. The expand() method is how Gradle

does this.

The expand() method takes advantage of the Groovy SimpleTemplateEngine class.

SimpleTemplateEngine adds a keyword substitution syntax to text files similar to the

syntax of Groovy string interpolation. Any string inside curly braces preceded by a dollar

sign (${string}) is a candidate for substitution. When declaring keyword expansion

in a copy task, you must pass a map to the expand() method (Example 1-8). The keys

in the map will be matched to the expressions inside curly braces in the copied file,

which will be replaced with the map’s corresponding values.

Example 1-8. Copying a file with keyword expansion

versionId = '1.6'

task copyProductionConfig(type: Copy) {

from 'source'

include 'config.properties'

into 'build/war/WEB-INF/config'

expand([

databaseHostname: 'db.company.com',

version: versionId,

buildNumber: (int)(Math.random() * 1000),

date: new Date()

])

}

SimpleTemplateEngine has some other features that are exposed to

you when you use the expand() method inside a copy task. Consult

the online documentation for more details.

Note that the expression passed to the expand()

method is a Groovy map literal—it is

enclosed by square brackets, and a series of key/value pairs are delimited by commas,

with the key and the value themselves separated by colons. In this example, the task

doing the expanding is dedicated to preparing a configuration file for the production

configuration, so the map can be expressed as a literal. A real-world build may opt for

this approach, or may reach out to other, environment-specific config file fragments for

the map data. Ultimately, the map passed to expand() can come from anywhere. The

fact that the Gradle build file is executable Groovy code gives you nearly unlimited

flexibility in deciding on its origin.

It’s helpful in this case to take a look at the source file, so we can directly see where the

string substitution is happening.

Filtering and Transforming Files | 5

www.it-ebooks.info

剩余79页未读，继续阅读

daisuo2599

粉丝: 4
资源: 115

Gradle进阶教程：超越基础

[Gradle.Beyond.the.Basics(2013.7)].Tim.Berglund.文字版

Gradle_Beyond_the_Basics

gradle入门介绍

gradle入门书

[Gradle] Gradle 进阶教程 (英文版)

深入理解Gradle：进阶指南

Gradle进阶指南：超越基础教程

Gradle进阶指南：Tim Berglund著2013版

Gradle进阶指南：解锁API、插件开发与构建复杂性管理

基于python与Django的网上购物平台

最新资源