BAML Java quickstart

The complete setup is one plugin line — write BAML in baml_src/, build, done:

// build.gradle.kts
plugins {
    java
    application
    id("com.boundaryml.baml") version "0.15.1-nightly.20260723.g"
}
repositories { mavenCentral() }

The plugin, runtime artifacts, and baml CLI publish together at one family version; the version in the plugins block must match your installed CLI. This example pins a published, end-to-end-verified version. Stable plugin versions resolve from the Gradle Plugin Portal with zero configuration; for nightlies (published to Maven Central) the example's settings.gradle.kts carries the standard pluginManagement stanza so resolution rests on documented Gradle behavior rather than the Portal's Central-proxying.

The plugin resolves from the Gradle Plugin Portal, runs baml generate before compilation (incrementally — it reruns only when a generation input changes: the .baml sources, baml.toml, or the resolved CLI version), registers the generated sources for the compiler and IDE, and injects the version-locked com.boundaryml:baml-bridge runtime plus the correct natives-<platform> jar for your machine (Kotlin projects also get baml-bridge-kotlin). Overrides live on the baml {} extension (nativePlatforms, manageDependencies, bamlExecutable).

Requirements: JDK 17+, the baml CLI on PATH at a version matching the plugin (install via the standard BAML install flow — the CLI, plugin, and runtime artifacts publish together at one version).

Run it:

gradle run
# add(2, 3) = 5