CLI reference

Barista has its own “signature” verbs for resolution and caching, plus drop-in synonyms for the Maven lifecycle phases. This page marks which commands execute in this pre-release and which are still being wired up.

Signature commands

CommandWhat it doesKey flags
barista pullResolve the dependency graph, fetch artifacts into the content-addressed cache, hardlink them into ~/.m2/repository, and write barista.lock.--update, --scope, --no-fetch, --explain
barista grind treePrint the resolved dependency graph.--format text|json
barista pourMaterialize locked artifacts into a target directory (default ~/.m2/repository) without re-resolving.--target, --scope, --dry-run
barista dial-inInteractive configuration wizard (writes ~/.barista/config.toml).--non-interactive, --output-path, --force
barista wrapperGenerate baristaw wrapper scripts in the project root.--version, --distribution-url, --checksum, --force
barista shot <phase>Run a one-off command on the warm path, skipping resolve+pour when the lockfile, daemon, and pom.xml are unchanged. Unix only in v0.1.
barista tapRegister and inspect taps (remote cache / worker endpoints): add, list, remove, status. Registration and health-probing only — routing build actions to a tap is not implemented in v0.1.

grind also defines diff, audit, and whysubcommands; these are placeholders that report “not yet implemented” in this build.

Maven lifecycle commands

clean, compile, test, package, verify, install, deploy, and site are drop-in synonyms for mvn <phase>. On macOS and Linux they execute through the warm-JVM barback daemon (embedded Maven 4), building byte-identically to Maven — single-module proven, multi-module reactor maturing; the daemon needs a JDK. On Windows, lifecycle execution isn’t wired yet: they print a “not yet executable” notice — pass --no-daemon to fork to your installed mvn.

Global flags

These apply to every subcommand:

FlagEffect
--output human|json|ndjsonOutput format. Default human.
--ciMacro expanding to --frozen --output json --quiet.
--frozenTreat barista.lock as authoritative; error if resolution would change it.
--strictStrict resolution — error on unresolvable version conflicts.
--maven-compat auto|3.9|4.0Maven compatibility mode. Default auto.
--no-daemonFork to upstream mvn instead of routing through barback.
--root PATH / -f, --file PATHOverride project-root discovery.
--config PATHOverride the barista.toml path.
--quiet / -v, --verbose / --no-colorOutput verbosity and color control.