elide build turns your elide.pkl manifest into a task graph: tasks are derived from your source sets and artifacts, wired together by their dependencies, and executed in order. Tasks are cached, so an unchanged task is skipped on the next build.
Running the build
elide build # run the default task group
elide build compile-java-main # run a specific task by name
elide build clean # run the special clean target
elide build --inspect # print the task graph without running it
elide build --no-cache # ignore cached results and rebuild
Task targets
A bare argument selects a single task by name, for example elide build compile-java-main, including special targets such as clean. A leading colon (:compile-java-main) is still accepted for backward compatibility but is no longer required. With no target, Elide runs the default task group.
Task groups
Tasks are organized into groups:
| Group | Description |
|---|---|
default | The tasks run by a plain elide build. |
testing | Test tasks, run by elide test. |
Caching
Elide fingerprints each task’s inputs and records them in the build-state file (see Lockfiles & Build State). On the next build, tasks whose inputs are unchanged are reported up-to-date and skipped. --no-cache forces a full rebuild.