What Was Announced
JetBrains released IntelliJ IDEA 2026.1 Early Access Program (EAP) builds with full support for Java 26, which became GA on March 17, 2026. True to its tradition of day-one language support, IntelliJ IDEA understands all Java 26 features — including preview and incubator JEPs — from the moment the JDK was released. The March EAP builds also include meaningful debugging improvements for virtual threads and a new inspection for Lazy Constants.
JetBrains also published the Java Annotated Monthly for March 2026, their regular curated roundup of Java articles, talks, and resources.
Key Features and Changes
Full Java 26 Support
IntelliJ IDEA 2026.1 EAP understands all 10 JEPs in Java 26 from day one, including preview features that require --enable-preview. Code completion, inspections, quick-fixes, and refactorings all work correctly with Java 26 syntax. You can configure the project language level to Java 26 Preview to access experimental features with IDE assistance.
LazyConstant Inspection and Quick-Fix
Java 26 introduces the concept of Lazy Constants (JEP in second preview) — fields whose values are computed lazily on first access and then cached. IntelliJ IDEA 2026.1 adds an inspection that detects patterns in your code that are semantically equivalent to a lazy constant and offers a quick-fix to convert them, making it easy to adopt the new language feature incrementally.
Virtual Thread Debugger: Structured Concurrency Scopes
This is one of the more practically useful debugging improvements in recent memory. Virtual threads — introduced in Java 21 and increasingly adopted — are now grouped in the debugger by their structured concurrency scope rather than appearing as a flat list of thousands of threads. When using StructuredTaskScope, the debugger shows the parent scope and the child virtual threads it manages as a tree, making it dramatically easier to understand concurrent code execution and trace which subtask is blocked or failing.
Previously, debugging virtual-thread-heavy code in IntelliJ meant scrolling through a huge flat list of threads with no structural context. This change brings the debugger's mental model in line with how structured concurrency is designed to work.
One IntelliJ IDEA: End of the Split?
JetBrains signalled in March that they are reconsidering the long-standing Community vs. Ultimate edition split. A unified IntelliJ IDEA offering is being evaluated — details are sparse, but the direction suggests moving toward a single product with tiered licensing rather than feature-gated editions.
Why It Matters for Developers
The virtual thread debugger improvement has an immediate impact on anyone building high-throughput Java services using the virtual thread + structured concurrency pattern (Loom). Debugging concurrent request handling has been a known pain point; the scope-based grouping makes the debugger match how you reason about the code.
For teams evaluating migration to Java 26, the LazyConstant inspection lowers the adoption cost of the new feature — you do not need to manually audit your codebase for candidates.
Source
Read the original article — JetBrains Blog
