Bazel rules for Elide — Kotlin / Java compilation, JUnit Platform tests, code formatting, and native-image builds powered by the Elide runtime.

Status: pre-alpha. Public API is unstable. Pin a specific commit or wait for the first tagged release.

Elide consolidates a polyglot runtime, a Kotlin/Java toolchain, formatters (google-java-format, ktfmt), and ahead-of-time native-image into one binary. For Bazel monorepos this means:

• One hermetic toolchain instead of separate rules_java, rules_kotlin, and rules_graalvm toolchains, each with their own JDK pin.
• Native-image and formatters as first-class rules, not separate rulesets.
• One small set of rules to learn (elide_kotlin_library, elide_java_library, elide_native_image, elide_format, ...) instead of three overlapping ecosystems.

MODULE.bazel:

bazel_dep(name = "rules_elide", version = "0.0.0")

elide = use_extension("@rules_elide//elide:extensions.bzl", "elide")
elide.install(version = "latest", channel = "nightly")
use_repo(elide, "elide_toolchains")
register_toolchains("@elide_toolchains//:all")

BUILD.bazel:

load("@rules_elide//elide:defs.bzl", "elide_kotlin_binary", "elide_kotlin_library")

elide_kotlin_library(
    name = "lib",
    srcs = glob(["src/main/kotlin/**/*.kt"]),
)

elide_kotlin_binary(
    name = "app",
    srcs = ["Main.kt"],
    main_class = "MainKt",
    deps = [":lib"],
)

bazel run //:app

Providers: ElideToolchainInfo, ElideInfo (docs/providers.md). Top-level entry point: @rules_elide//elide:defs.bzl.

The elide module extension downloads the elide release artifact for the host platform from the public Elide CDN:

https://elide.zip/artifacts/{channel}/{version}/elide.{os}-{cpu}.{ext}

Each artifact is verified against an in-tree SRI integrity table.

• channel: nightly, preview, or release. Pre-alpha: only nightly and preview are populated upstream.
• version: any concrete revision (e.g. 1.2.0-beta) or the rolling pointer latest. With latest, integrity reflects the snapshot captured in elide/private/versions.bzl; if the CDN advances, regenerate the integrity row.

Supported platforms:

Windows is published on the CDN but not yet supported by these rules — the launcher templates are POSIX sh only. See Roadmap below.

MODULE.bazel.lock records the resolved hashes (the extension marks itself reproducible = True).

Every compile rule returns a complete JavaInfo:

• output_jar — the full class JAR produced by elide javac --jar / elide kotlinc -d.
• compile_jar — ABI jar derived via java_common.run_ijar for fast downstream incremental rebuilds.
• source_jars — sources packaged via java_common.pack_sources (IDE sync / Maven publish friendly).

elide_java_test and elide_kotlin_test launch the JUnit Platform ConsoleLauncher. The launcher honours Bazel's test runner contract: TEST_TMPDIR, XML_OUTPUT_FILE, and TEST_FILTER. Reports written to $TEST_TMPDIR/reports/ are merged into $XML_OUTPUT_FILE post-run.

Consumer requirement: place org.junit.platform:junit-platform-console-standalone on the test classpath via runtime_deps (typically through rules_jvm_external).

Use test_class = "<fqcn>" to select a single class; leave empty to scan the classpath.

load("@rules_elide//elide:defs.bzl", "elide_format")

elide_format(
    name = "format",
    srcs = glob(["src/**/*.kt"]) + glob(["src/**/*.java"]),
)

bazel run //:format formats files in place. Java sources route through google-java-format; .kt/.kts route through ktfmt. A single target may not mix languages — split into two elide_format targets if needed.

• No host JDK detection. No repository_ctx.which. The full extracted elide distribution is declared as runfiles of the toolchain.
• Platform-resolved via @platforms//os:* + @platforms//cpu:*.
• All file paths are relative; no developer-machine paths leak into outputs. Should run unchanged under Buildfarm, BuildBuddy RBE, or EngFlow remote execution.

rules_elide returns JavaInfo from every compile rule, so existing java_library / kt_jvm_library consumers can depend on elide_* targets unchanged.

See benchmarks/RESULTS.md for methodology, recorded numbers, and how to reproduce locally via ./benchmarks/bench.sh.

To validate the smoke workspace against a locally-built elide binary, point ELIDE_DEV_BIN at the binary and enable --config=dev in e2e/smoke/:

ELIDE_DEV_BIN=/abs/path/to/elide bazel build //... --config=dev
ELIDE_DEV_BIN=/abs/path/to/elide bazel test  //... --config=dev

See e2e/smoke/README.md for the full flow.

Semantic versioning. compatibility_level = 1 until a hard API break.

Releases are automated via release-please and published to GitHub Releases and the Bazel Central Registry with Sigstore-signed build provenance and SBOMs. See RELEASING.md for details.

Apache 2.0. See LICENSE.

See CONTRIBUTING.md.