What’s New in IntelliJ IDEA 2022.2 Beta? Remote Development, Spring 6 Support, and More
IntelliJ IDEA 2022.2 beta introduces a split remote‑development architecture, full Spring 6 and Spring Boot 3 support, global font‑size shortcuts, clickable URLs in config files, an experimental GraalVM native debugger, enhanced bean‑validation handling, upgraded Kubernetes/Docker, and numerous IDE improvements for Java developers.
IntelliJ IDEA 2022.2 beta has been released, introducing a split remote development architecture where the IDE runs as a backend service on a remote server and a thin client provides the UI locally via SSH.
It fully supports the new features of Spring 6 and Spring Boot 3, including @AutoConfiguration and @ConfigurationProperties classes.
New global shortcuts allow changing the editor font size (Ctrl+Shift+., Alt+Shift+.) and clickable URLs are now enabled in JSON, YAML and .properties files.
An experimental GraalVM native debugger lets you debug native images and automatically creates run configurations for Maven/Gradle projects (requires a GraalVM development build and plugin).
Bean validation annotations now show references and support folding for Java and Kotlin.
Groovy integration queries support.
Built‑in Kubernetes and Docker versions have been upgraded.
Run Current File feature enables running or debugging a single file without a dedicated run configuration.
Trusted SSL certificates can be imported.
HTTP client has been improved.
IDE runtime switched from JBR11 to JBR17.
Enhanced code inspection and completion for Java.
Improved configuration file handling.
For the full list of changes see the official release announcement.
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.