/*
            Note: we currently extract this information from the execution plan because it's
            buried under functions in #filter. This could be detangled/simplified by introducing
            excludeTasks(Iterable<Task>) as an analog to addEntryTasks(Iterable<Task>).

            This is too drastic a change for the stage in the release cycle were exposing this information

----
$ gradle dist --exclude-task test
----
----
include::{snippetsPath}/tutorial/excludeTasks/tests/excludeTask.out[]
----

.Simple Task Graph
image::commandLineTutorialTasks.png[]

You can see that the `test` task is not executed, even though the `dist` task depends on it.

# tag::cli[]
# gradle dist --exclude-task=test
# end::cli[]
executable: gradle
args: dist
flags: "--exclude-task=test"

Laura Kassovic <******@****.***> 1701107622 -0800