Skip to main content
The framework story is identical to Java — the container injects the same shared RepostRuntime, and the plugin’s integration selection registers your generated client as a bean.
  • Spring Boot — add sh.repost:repost-client-spring-boot-starter, set integration to SPRING_BOOT, configure repost.client.* properties, and inject your RepostClient. Compiled against Spring Boot 4.0.7, verified on 4.1.0. See the Java framework guide for the full property key set, override beans, lifecycle, and observability.
  • Jakarta CDI / MicroProfile — add sh.repost:repost-client-cdi, set integration to CDI, and @Inject your client. Built against Jakarta CDI 4.0.1 and MicroProfile Config 3.1.
  • Ktor — certified on 3.5.1. The coroutine DSL drops straight into a Ktor route; scope one RepostClient to the application lifecycle and close() it on shutdown.
  • Vert.x — certified on 4.5.29 and 5.1.4 via the CompletionStage (createdOperation) API on the event loop.
  • Quarkus / Micronaut — the framework-neutral core works today (produce a RepostRuntime bean, then a borrowed client via RepostClient.fromRuntime(runtime), and wire close to the container hook), but dedicated extensions and native certification are post-GA. See the Java framework guide for the tested pattern.

​
Continue

Compatibility & security

The supported Kotlin, Gradle, JDK, and framework matrix and the security posture.

Configuration

The options behind the repost.client.* property keys.

Java framework guide

The full Spring Boot and CDI reference the Kotlin integrations share.