rnett
08/09/2026, 12:26 AMRey (Kingg22)
08/09/2026, 1:00 AMYoussef Shoaib [MOD]
08/09/2026, 1:21 AMdev version (i.e. cut from master), and it sometimes even has IDE-specific commits on top.
The onus thus falls on plugin developers to build and release their plugins against IDE versions.
KEFS offers a useful convention to choose a different release of a compiler plugin based on the Kotlin version it has in its version. (It does other cool things like improving stability and such)
Metro is the trailblazer here: it loads at runtime different compatibility layers to change its behavior based on the compiler version. It thus doesn't even need KEFS, just the registry setting.
TL;DR: you already can use compiler plugins in IDE (with a registry option), but compatibility is hit-or-miss unless the plugin developer specifically designed for it (either by releasing multiple versions, like TestBalloon does, or changing behavior at runtime, like Metro does)Youssef Shoaib [MOD]
11/10/2026, 3:28 AMMANIFEST.MF attributes
These same attributes are setup by the just-announced compiler plugin DevKit: https://kotlinlang.slack.com/archives/C7L3JB43G/p1794279994955089