IntelliJ Platform Projects Migrated to Java 17 – What It Means for Plugin Developers
The IntelliJ platform has moved its source code to Java 17, requiring IDE 2022.3 to run on Java 17 while still supporting some modules for older Java versions, and this shift impacts plugin development, version compatibility, and build processes for developers.
JetBrains announced that the source code of the IntelliJ platform has recently been migrated to Java 17.
Although some modules are still compiled for older Java versions to maintain compatibility, the majority of platform and plugin modules now use Java 17, and the upcoming IntelliJ‑based IDE version 2022.3 will require Java 17 to start.
What this means for users
If you develop plugins, you can use the new language features and APIs of Java 17, provided that the 223 attribute is set in plugin.xml .
If your plugin needs to run on multiple IDE versions, such as 2022.3 and 2022.2 , you must continue using Java 11 for compatibility.
To compile the intellij‑community project, simply invoke the Build Project action; IntelliJ IDEA will suggest automatically downloading 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/
Advertisement: Need a genuine JetBrains All‑Products Pack? Contact me for ¥56 per year, genuine license, verified on the official site. Add me on WeChat: poxiaozhiai6, note: 902.
Discussion: The migration of IntelliJ project source code to Java 17 has sparked online debate – what do you think?
Java Captain
Focused on Java technologies: SSM, the Spring ecosystem, microservices, MySQL, MyCat, clustering, distributed systems, middleware, Linux, networking, multithreading; occasionally covers DevOps tools like Jenkins, Nexus, Docker, ELK; shares practical tech insights and is dedicated to full‑stack Java development.
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.