Skip to content
MosaicMosaic

Compatibility

Runtime supports Kotlin/JVM on Java 17+, using Kotlin language/API level 2.2. Optional Analysis requires matching Kotlin compiler and Kotlin Gradle Plugin (KGP) versions within its supported project boundary.

Mosaic supports each Kotlin minor family for 18 months after its first stable release, including stable patches. Kotlin range boundaries expand after verification; prereleases are excluded.

The tables show inclusive ranges: every published stable version between the endpoints is supported. With optional Analysis, your Runtime must be in its Runtime range, and your Kotlin version must be in both releases’ Kotlin ranges. The effective Kotlin range is their overlap. Official Kotlin support follows the 18-month window; historical compatibility ranges remain available afterward.

Runtime and Kotlin
RuntimeKotlin
1.1.02.2.0–2.4.21
1.0.02.2.0–2.4.21
Analysis, Runtime, and Kotlin
AnalysisRuntimeKotlin/KGP
1.0.11.0.0–1.1.02.2.0–2.4.21
1.0.01.0.0–1.1.02.2.0–2.4.21

The optional Analysis plugin supports consumer Gradle versions 8.2.1 through 9.7.1, within the Gradle range supported by your KGP version. The Gradle JVM must be Java 17 or newer and supported by that Gradle distribution. Use Java 17 with Gradle 8.2.1; running Gradle on Java 21 requires Gradle 8.5 or newer.

Real Kotlin DSL applications exercise these representative combinations using the published plugin marker and Maven artifacts:

Consumer Gradle Kotlin / KGP
8.2.1 2.4.21
9.0.0 2.3.0
9.7.1 2.4.21

These checks cover application compilation and execution, compiler artifact selection, extraction, verification diagnostics, packaged summaries, and configuration-cache storage and reuse. The build wrapper used to produce Mosaic does not establish the consumer Gradle requirement. Isolated-project compatibility is not established.

Mosaic follows semantic versioning for stable Runtime APIs, covering Kotlin source compatibility, JVM binary compatibility, and documented behavior. Minor releases may add compatible capabilities; breaking changes normally belong in major releases. Deprecations provide migration guidance with timing appropriate to the change. The Runtime ABI validator protects existing JVM signatures.

Keep mosaic-core, mosaic-test, and mosaic-opentelemetry at the same Runtime version; the BOM aligns these modules. Analysis releases independently and is outside the BOM. Runtime and Analysis versions need not match when their compatibility ranges overlap.

Analysis APIs, configuration, metadata, diagnostics, and reports remain provisional, with migration guidance for breaking changes. The plugin selects its compiler integration automatically; use a verified combination above.

Missing dependency metadata and unsupported paths remain UNVERIFIED. Present but incompatible metadata fails, and unsupported Runtime semantics never silently become VERIFIED. Regenerate incompatible summaries with compatible tooling. A STANDARD pass with warnings does not prove every lookup safe; STRICT also fails uncertainty.

See the 1.0 migration notes when upgrading from 0.7.0.