Task + Project + Facts -> Plan. Pure and total.
A release is a value before it is an effect. Everything read from the
filesystem or the network already sits in facts, so the whole decision —
which jar, whether to skip, what gets published where — can be asserted
without building anything.
Adding a task is a new steps method; adding a destination is a
publish/register!. Neither edits an existing branch.
Task + Project + Facts -> Plan. Pure and total. A release is a value before it is an effect. Everything read from the filesystem or the network already sits in `facts`, so the whole decision — which jar, whether to skip, what gets published where — can be asserted without building anything. Adding a task is a new `steps` method; adding a destination is a `publish/register!`. Neither edits an existing branch.
(artifact-task kind)The build task that produces kind.
The build task that produces `kind`.
(builds-jar? plan)True when plan produces a jar.
True when `plan` produces a jar.
(compiles? task project)True when task on project will AOT-compile.
Only a compiling task consults ./local.deps.edn, so a source-jar build never depends on — or fails on — a developer's local overlay file.
True when `task` on `project` will AOT-compile. Only a compiling task consults ./local.deps.edn, so a source-jar build never depends on — or fails on — a developer's local overlay file.
(plan task project facts)The Plan for task on project, given facts.
The Plan for `task` on `project`, given `facts`.
(publishes? plan)True when running plan would push an artifact to a registry.
True when running `plan` would push an artifact to a registry.
Steps for one task. Dispatches on the task keyword.
Steps for one task. Dispatches on the task keyword.
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |