KITFORMA · EDITORIAL GUIDE
How do I diagnose an unsupported class version inside a Gradle plugin?
KitForma editorial guide. The incompatible bytecode may belong to a build plugin rather than the application. Lowering the application target cannot rewrite a plugin already compiled for a newer JVM.
Step-by-step guidance
The incompatible bytecode may belong to a build plugin rather than the application. Lowering the application target cannot rewrite a plugin already compiled for a newer JVM.
Read the failing class and stack trace, record wrapper and daemon JVM versions, then compare plugin requirements with Gradle’s runtime matrix. Choose a mutually supported combination or an appropriate plugin release. Keep the application toolchain decision separate.
Run the smallest task loading that plugin before compiling application sources. Not every unsupported-major-version error calls for the same JDK upgrade: a newer daemon can itself be unsupported by an older wrapper. Verify the full combination in CI.
Sources and verification
Sources checked:
Scope: This editorial guide is based on the cited sources and tool behavior. A forum question or a query observed for our site does not establish market search volume, low competition, guaranteed rankings or inadequate answers elsewhere.
This starter guide was prepared by KitForma with AI assistance. It is not presented as a real member question or an independent user review. Check the sources and the result with your own file; report corrections in the discussion.