Summary
- IntelliJ version 2025.1.4 focuses on fixing issues rather than adding new features.
- Dart closing labels now appear as inlay hints, allowing more user customization.
- The update resolves false-positive warnings with @Configuration classes and fixes HTTP Client feature.
IntelliJ is one of the most popular integrated development environments (IDEs) out there, with a focus on Java and Kotlin. And now, it’s getting even better with the addition of a few new changes that will make the experience better.
JetBrains is rolling out version 2025.1.4 of the IntelliJ IDE. This update seems to be mostly focused on fixing issues rather than introducing new features. One of the few user-facing changes in this release is an update to how closing labels are handled in the Dart programming language. Previously, these labels, which help identify the corresponding start of a widget or code block, have been redesigned to appear as inlay hints. Developers now have more granular control over the visibility and appearance of these hints, allowing them to tailor the editor to their personal preferences and coding style.
Related
IntelliJ IDE Gets New Free Features With Edition Merge
No more separate downloads for Community Edition and Ultimate Edition.
For developers working with the Java Spring framework, the update resolves a persistent issue that was causing false-positive warnings. A warning stating that a “Final declaration can’t be overridden at runtime” was incorrectly being triggered for classes annotated with @Configuration that used the default proxyBeanMethods=true setting. Another significant fix addresses a regression in the IDE’s powerful built-in HTTP Client. Functionality that allowed users to override variables from imported .http files had been unintentionally broken in a previous version. This feature is critical for developers who manage different testing environments (such as development, staging, and production) by defining variables in separate files.
Finally, the v2025.1 update tackles a complex build issue affecting certain Maven projects. Developers working with artifacts that contained circular dependencies between .main and .testwar exploded types were encountering build failures within the IDE. The logic in the build system has now been adjusted to correctly handle this specific dependency structure.
The main points from the official changelog are listed below.
- Closing labels in Dart have been updated for better usability and now appear as inlay hints, with improved configuration options. [IDEA-289260]
- The Final declaration can’t be overridden at runtime warning no longer falsely appears for @Configuration classes with proxyBeanMethods. [IDEA-304648]
- It is once again possible to override variables from imported .http files in the HTTP Client. [IJPL-190688]
- Artifacts with circular dependencies between .main and .testwar exploded types can now be built correctly when working with Maven projects. [IDEA-371537]
There are a lot of other changes, which you can check out on the update’s longer release notes. The update is now live, so if IntelliJ is a part of your daily development workflow, you should download it now.
Source: JetBrains