Skip to content

build: pin JVM target 21 for modules on sk.ainet.multiplatform 1.1.0 - #442

Merged
michalharakal merged 1 commit into
developfrom
fix/convention-plugin-jvm-target-21
Sep 20, 2026
Merged

michalharakal merged 1 commit into
developfrom
fix/convention-plugin-jvm-target-21

Conversation

@michalharakal

Copy link
Copy Markdown
Contributor

develop has been red since the sk.ainet.* convention plugins went 1.0.0 → 1.1.0 (#437#439). 1.1.0 adds a jvmTarget option to the skainet { } extension with default JVM 17, which overrides the root build's JVM 21 for the three modules that apply the plugin (asr-domain, llm-core, transformer-core). Inline calls into the JVM-21 engine artifacts then fail:

e: .../transformer-core/.../Embedding.kt:101:39 Cannot inline bytecode built with JVM target 21 into bytecode that is being built with JVM target 17.

Fix: set jvmTarget = JvmTarget.JVM_21 in those three skainet { } blocks.

Verified locally: same checkout fails with 1.1.0, passes with 1.0.0, and passes with 1.1.0 + this change (:asr-domain, :llm-core, :transformer-core, :llm-inference:functiongemma compileKotlinJvm).

Convention plugin 1.1.0 introduces a jvmTarget option defaulting to JVM 17. asr-domain,
llm-core and transformer-core were therefore compiled for 17 while the engine artifacts
and the rest of the build are 21, and inline calls into the engine no longer compile
("Cannot inline bytecode built with JVM target 21 into ... 17"). develop has been red
since the 1.0.0 -> 1.1.0 plugin bump.
@michalharakal
michalharakal merged commit 701d529 into develop Sep 20, 2026
2 checks passed
@michalharakal
michalharakal deleted the fix/convention-plugin-jvm-target-21 branch September 20, 2026 13:02
@michalharakal michalharakal mentioned this pull request Sep 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant