Gradle Goodness: Working with Live Task Collection
Gradle support the definition of so called live collections. These collections are mostly created based on criteria like with a filter() or matching() method. The collection content can change if the content of the source collection changes. For example the org.gradle.api.DomainObjectCollection interface has a matching method that returns a live collection. The list of tasks in a project implements this interface so we can have a live collection of tasks that match a certain criteria.
The nice thing about the live collection of tasks is that we can add tasks to the project after we have defined the task collection and they will be included in the collection. Normally if we would access the list of tasks in a project and use for example a findAll method than the returned list of tasks will not change. So if we add a new task to the project it will not be added to the list of task that apply to the condition of the findAll method.
Now if we use the matching() method on a list of tasks the result will be a live list of tasks. Even if we add tasks to the project after the definition of the list of tasks, they will be added to the collection.
Let's see the following Gradle build file that defines the tasks allCompile and allCopy. Each task has dependencies on other tasks. We use the dependsOn() method of a task to set those dependencies. The dependsOn() method accepts a collection of other tasks. For the allCompile task we don't use a live collection and for the allCopy task we use a live collection.
00.task allCompile << {01.println 'All is compiled.'02.}03.allCompile.dependsOn project.tasks.findAll {04.it.name.startsWith('compile')05.}06. 07.task allCopy << {08.println 'Everything is copied.'09.}10.// Set dependencies with live collection of tasks.11.allCopy.dependsOn project.tasks.matching {12.it.name.startsWith('copy')13.}14. 15.// Add dependency tasks.16.5.times {17.// Dependencies for compileAll task.18.task "compile${it}" << { println 'Compile the code.' }19. 20.// Dependencies for copyAll task.21.task "copy${it}" << { println 'Copy something.' }22.}If we run the build script we get the following output:
$ gradle allCompile allCopy:allCompileAll is compiled.:copy0Copy something.:copy1Copy something.:copy2Copy something.:copy3Copy something.:copy4Copy something.:allCopyEverything is copied.BUILD SUCCESSFULTotal time: 2.232 secsWe notice the allCompile tasks doesn't have any dependencies, because those task dependencies didn't exist when we used the dependsOn() method. The allCopy task has all task dependencies even though we created them later in the build script.
Bonus: we can use the findAll method to look for task dependencies, but we have to let Gradle evaluate this condition in a closure. So we can change our build script and use a closure with the dependsOn() method. Gradle will invoke the closure at execution time and not a configuration time. The dependencies tasks are then available and assigned as dependencies to the allCompile task:
00.task allCompile << {01.println 'All is compiled.'02.}03.// Use closure for resolving task dependencies.04.allCompile.dependsOn {05.project.tasks.findAll {06.it.name.startsWith('compile')07.}08.}09. 10.task allCopy << {11.println 'Everything is copied.'12.}13.// Set dependencies with live collection of tasks.14.allCopy.dependsOn project.tasks.matching {15.it.name.startsWith('copy')16.}17. 18.// Add dependency tasks.19.5.times {20.// Dependencies for compileAll task.21.task "compile${it}" << { println 'Compile the code.' }22. 23.// Dependencies for copyAll task.24.task "copy${it}" << { println 'Copy something.' }25.}If we invoke both tasks with Gradle we get the following output:
:compile0Compile the code.:compile1Compile the code.:compile2Compile the code.:compile3Compile the code.:compile4Compile the code.:allCompileAll is compiled.:copy0Copy something.:copy1Copy something.:copy2Copy something.:copy3Copy something.:copy4Copy something.:allCopyEverything is copied.BUILD SUCCESSFULTotal time: 2.258 secsThis blog post is based on Gradle version 1.0-rc-3
Gradle Goodness: Working with Live Task Collection的更多相关文章
- Gradle Goodness: Task Output Annotations Create Directory Automatically
Gradle Goodness: Task Output Annotations Create Directory Automatically One of the great features of ...
- Gradle Goodness: Copy Files with Filtering
Gradle Goodness: Copy Files with Filtering Gradle's copy task is very powerful and includes filterin ...
- Gradle Goodness: Init Script for Adding Extra Plugins to Existing Projects
Gradle Goodness: Init Script for Adding Extra Plugins to Existing Projects Gradle is very flexible. ...
- Gradle Goodness: Group Similar Tasks
In Gradle we can assign a task to a group. Gradle uses the group for example in the output of $ grad ...
- Gradle Goodness: Add Incremental Build Support to Tasks
Gradle has a very powerful incremental build feature. This means Gradle will not execute a task unle ...
- Gradle Goodness: Rename Ant Task Names When Importing Ant Build File
Migrating from Ant to Gradle is very easy with the importBuild method from AntBuilder. We only have ...
- Gradle Goodness: Parse Files with SimpleTemplateEngine in Copy Task
With the copy task of Gradle we can copy files that are parsed by Groovy's SimpleTemplateEngine. Thi ...
- Gradle Goodness: Check Task Dependencies With a Dry Run
We can run a Gradle build without any of the task actions being executed. This is a so-called dry ru ...
- Gradle Goodness: Using and Working with Gradle Version
To get the current Gradle version we can use the gradleVersion property of the Gradle object. This r ...
随机推荐
- IoDH 实现的单例模式
饿汉式单例类不能实现延迟加载,不管将来用不用始终占据内存:懒汉式单例类线程安全控制烦琐,而且性能受影响.有种更好的单例模式叫做Initialization Demand Holder (IoDH)的技 ...
- javascript刷新页面的集中办法
1. history.go(0) 2. location.reload() 3. location=location 4. location.assign(location) 5. document. ...
- winform判断chrome是否正在最前端运行
/// <summary> /// 获取系统当前活动窗口 /// </summary> /// <returns></returns> [DllImpo ...
- sql left join 字符串
select * FROM table1 as t1 right join (select '1,2,3,4,5' as t) as tt on t1.Id=tt.t select * FROM t ...
- Java基础_day01
一.JRE和JDK的安装, JRE —— Java 运行环境 Java runtime environment 包含Java虚拟机和Java程序的核心类库. ...
- React Native之React速学教程(上)
概述 本篇为<React Native之React速学教程>的第一篇.本篇将从React的特点.如何使用React.JSX语法.组件(Component)以及组件的属性,状态等方面进行讲解 ...
- ArcGIS DataStore手册——入门篇
第一章:ArcGIS DataStore入门 1.ArcGIS DataStore简介 ArcGIS DataStore是ArcGIS10.3推出来的一个全新的组件,它是一个关系型数据库管理系统,用于 ...
- 考勤机sql语句
考勤机sql语句 SELECT checkinout.id as 序号 ,checkinout.pin as 打卡编号,userinfo.name 姓名, checkinout.checktime 签 ...
- Android ListView复制、删除的实现
适配器MyAdapter: package com.zihao.adapter; import java.util.List; import com.zihao.popdemo.R; import c ...
- [转] RISC-V架构介绍
1. RISC-V和其他开放架构有何不同 如果仅从"免费"或"开放"这两点来评判,RISC-V架构并不是第一个做到免费或开放的处理器架构. 在开始之前,我们先通 ...