Examples of org.gradle.api.Task

org.gradle.api.Task
A Task represents a single atomic piece of work for a build, such as compiling classes or generating javadoc.

Each task belongs to a {@link Project}. You can use the various methods on {@link org.gradle.api.tasks.TaskContainer} to create and lookup task instances. For example, {@link org.gradle.api.tasks.TaskContainer#add(String)} creates an empty task with the given name. You can also use the{@code task} keyword in your build file:
```
 task myTask task myTask { configure closure } task myType << { task action } task myTask(type: SomeType) task myTask(type: SomeType) { configure closure } 
```
Each task has a name, which can be used to refer to the task within its owning project, and a fully qualified path, which is unique across all tasks in all projects. The path is the concatenation of the owning project's path and the task's name. Path elements are separated using the {@value org.gradle.api.Project#PATH_SEPARATOR}character.

Task Actions

A Task is made up of a sequence of {@link Action} objects. When the task is executed, each of theactions is executed in turn, by calling {@link Action#execute}. You can add actions to a task by calling {@link #doFirst(Action)} or {@link #doLast(Action)}.

Groovy closures can also be used to provide a task action. When the action is executed, the closure is called with the task as parameter. You can add action closures to a task by calling {@link #doFirst(groovy.lang.Closure)} or{@link #doLast(groovy.lang.Closure)} or using the left-shift << operator.
There are 2 special exceptions which a task action can throw to abort execution and continue without failing the build. A task action can abort execution of the action and continue to the next action of the task by throwing a {@link org.gradle.api.tasks.StopActionException}. A task action can abort execution of the task and continue to the next task by throwing a {@link org.gradle.api.tasks.StopExecutionException}. Using these exceptions allows you to have precondition actions which skip execution of the task, or part of the task, if not true.
Dependencies

A task may have dependencies on other tasks. Gradle ensures that tasks are executed in dependency order, so that the dependencies of a task are executed before the task is executed. You can add dependencies to a task using {@link #dependsOn(Object)} or {@link #setDependsOn(Iterable)}. You can add objects of any of the following types as a dependency:
- A {@code String} task path or name. A relative path is interpreted relative to the task's {@link Project}. This allows you to refer to tasks in other projects.
- A {@link Task}.
- A closure. The closure may take a {@code Task} as parameter. It may return any of the types listed here. Itsreturn value is recursively converted to tasks. A {@code null} return value is treated as an empty collection.
- A {@link TaskDependency} object.
- A {@link Buildable} object.
- A {@code Collection}, {@code Map} or an array. May contain any of the types listed here. The elements of thecollection/map/array are recursively converted to tasks.
- A {@code Callable}. The {@code call()} method may return any of the types listed here. Its return value isrecursively converted to tasks. A {@code null} return value is treated as an empty collection.
- An {@code Object}. The object's {@code toString()} method is interpreted as a task path or name.
Using a Task in a Build File
Dynamic Properties

A {@code Task} has 3 'scopes' for properties. You can access these properties by name from the build file or bycalling the {@link #property(String)} method.
- The {@code Task} object itself. This includes any property getters and setters declared by the {@code Task}implementation class. The properties of this scope are readable or writable based on the presence of the corresponding getter and setter methods.
- The additional properties of the task. Each task object maintains a map of additional properties. These are arbitrary name -> value pairs which you can use to dynamically add properties to a task object. The properties of this scope are readable and writable.
- The convention properties added to the task by each {@link Plugin} applied to the project. A {@link Plugin} can add properties and methods to a task through the task's {@link Convention} object. The properties ofthis scope may be readable or writable, depending on the convention objects.
Dynamic Methods

A {@link Plugin} may add methods to a {@code Task} using its {@link Convention} object.
@author Hans Dockter

        Map<String, Object> mutableOptions = new HashMap<String, Object>(options);


        Object replaceStr = mutableOptions.remove(Task.TASK_OVERWRITE);
        boolean replace = replaceStr != null && "true".equals(replaceStr.toString());


        Task task = taskFactory.createTask(project, mutableOptions);
        String name = task.getName();


        if (!replace && findByNameWithoutRules(name) != null) {
            throw new InvalidUserDataException(String.format(
                    "Cannot add %s as a task with that name already exists.", task));
        }

View Full Code Here

        }
        return getByPath(path.toString());
    }


    public Task getByPath(String path) throws UnknownTaskException {
        Task task = findByPath(path);
        if (task == null) {
            throw new UnknownTaskException(String.format("Task with path '%s' not found in %s.", path, project));
        }
        return task;
    }

View Full Code Here

        taskExecuter = new DefaultTaskGraphExecuter(listenerManager);
    }


    @Test
    public void testExecutesTasksInDependencyOrder() {
        Task a = createTask("a");
        Task b = createTask("b", a);
        Task c = createTask("c", b, a);
        Task d = createTask("d", c);


        taskExecuter.execute(toList(d));


        assertThat(executedTasks, equalTo(toList(a, b, c, d)));
    }

View Full Code Here

        assertThat(executedTasks, equalTo(toList(a, b, c, d)));
    }


    @Test
    public void testExecutesDependenciesInNameOrder() {
        Task a = createTask("a");
        Task b = createTask("b");
        Task c = createTask("c");
        Task d = createTask("d", b, a, c);


        taskExecuter.execute(toList(d));


        assertThat(executedTasks, equalTo(toList(a, b, c, d)));
    }

View Full Code Here

        assertThat(executedTasks, equalTo(toList(a, b, c, d)));
    }


    @Test
    public void testExecutesTasksInASingleBatchInNameOrder() {
        Task a = createTask("a");
        Task b = createTask("b");
        Task c = createTask("c");


        taskExecuter.execute(toList(b, c, a));


        assertThat(executedTasks, equalTo(toList(a, b, c)));
    }

View Full Code Here

        assertThat(executedTasks, equalTo(toList(a, b, c)));
    }


    @Test
    public void testExecutesBatchesInOrderAdded() {
        Task a = createTask("a");
        Task b = createTask("b");
        Task c = createTask("c");
        Task d = createTask("d");


        taskExecuter.addTasks(toList(c, b));
        taskExecuter.addTasks(toList(d, a));
        taskExecuter.execute();

View Full Code Here

        assertThat(executedTasks, equalTo(toList(b, c, a, d)));
    }


    @Test
    public void testExecutesSharedDependenciesOfBatchesOnceOnly() {
        Task a = createTask("a");
        Task b = createTask("b");
        Task c = createTask("c", a, b);
        Task d = createTask("d");
        Task e = createTask("e", b, d);


        taskExecuter.addTasks(toList(c));
        taskExecuter.addTasks(toList(e));
        taskExecuter.execute();

View Full Code Here

        assertThat(executedTasks, equalTo(toList(a, b, c, d, e)));
    }


    @Test
    public void testAddTasksAddsDependencies() {
        Task a = createTask("a");
        Task b = createTask("b", a);
        Task c = createTask("c", b, a);
        Task d = createTask("d", c);
        taskExecuter.addTasks(toList(d));


        assertTrue(taskExecuter.hasTask(":a"));
        assertTrue(taskExecuter.hasTask(a));
        assertTrue(taskExecuter.hasTask(":b"));

View Full Code Here

        assertThat(taskExecuter.getAllTasks(), equalTo(toList(a, b, c, d)));
    }


    @Test
    public void testGetAllTasksReturnsTasksInExecutionOrder() {
        Task d = createTask("d");
        Task c = createTask("c");
        Task b = createTask("b", d, c);
        Task a = createTask("a", b);
        taskExecuter.addTasks(toList(a));


        assertThat(taskExecuter.getAllTasks(), equalTo(toList(c, d, b, a)));
    }

View Full Code Here

        }
    }


    @Test
    public void testDiscardsTasksAfterExecute() {
        Task a = createTask("a");
        Task b = createTask("b", a);


        taskExecuter.addTasks(toList(b));
        taskExecuter.execute();


        assertFalse(taskExecuter.hasTask(":a"));

View Full Code Here

0 1 2 3 4 5 6 7 8 9

TOP

Related Classes of org.gradle.api.Task

co.tomlee.gradle.plugins.release.ReleasePlugin

com.android.build.gradle.internal.VariantManager

edu.sc.seis.launch4j.Launch4jPlugin

net.minecraftforge.gradle.dev.DevBasePlugin

net.minecraftforge.gradle.dev.FmlDevPlugin

net.minecraftforge.gradle.dev.ForgeDevPlugin

net.minecraftforge.gradle.dev.McpcDevPlugin

net.minecraftforge.gradle.tasks.abstractutil.CachedTask

net.minecraftforge.gradle.user.lib.UserLibBasePlugin

net.minecraftforge.gradle.user.UserBasePlugin

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.

Examples of org.gradle.api.Task

Task Actions

Dependencies

Using a Task in a Build File

Dynamic Properties

Dynamic Methods

Related Classes of org.gradle.api.Task