Why IntelliJ IDEA Now Requires Java 17 and What It Means for Your Plugins
IntelliJ’s source code has moved to Java 17, meaning most platform and plugin modules now target Java 17, the 2022.3 IDE release requires it, and developers can use new language features by setting plugin.xml to 223, while still supporting older versions with Java 11.
JetBrains blog reports that the source code of IntelliJ projects has recently been migrated to Java 17.
While some modules are still compiled for older Java versions to maintain compatibility, the majority of platform and plugin modules now target Java 17, and the upcoming 2022.3 release of IntelliJ‑based IDEs requires Java 17 to launch.
What this means for developers
Plugins can leverage Java 17 language features and APIs, provided the plugin.xml languageLevel attribute is set to 223.
If a plugin must run on multiple IDE versions such as 2022.3 and 2022.2, it must continue to use Java 11.
To build the intellij-community project, simply invoke the “Build Project” action; IntelliJ IDEA will automatically download JetBrains Runtime 17 and set it as the project JDK.
Related link: https://blog.jetbrains.com/platform/2022/08/intellij-project-migrates-to-java-17/
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Programmer DD
A tinkering programmer and author of "Spring Cloud Microservices in Action"
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.