It resolved compatibility issues with Maven 3.6.0 , which previously caused issues in the IDE's internal build processing.
As the third bug-fix update of the 2018.3 branch, this version includes all the hallmark "Top" features introduced in that cycle:
The debut of initial support for GitHub PRs allowed developers to view, manage, and create local branches from PRs without leaving the IDE. jetbrains intellij idea ultimate 201833 top
For developers requiring high visibility, this release cycle introduced the , which can be enabled via Preferences | Appearance & Behavior . It also added support for Multiline TODO comments , allowing developers to group multiple lines under a single TODO task by indenting subsequent lines. The JetBrains Bloghttps://blog.jetbrains.com IntelliJ IDEA 2018.3 - The JetBrains Blog
Released in January 2019, serves as a vital stability and refinement update for the massive 2018.3 release cycle. This version focused on polishing advanced Ultimate-only features like the JVM Profiler while resolving critical regressions in Maven, version control, and Java 12 support. Key Enhancements in IntelliJ IDEA 2018.3.3 It resolved compatibility issues with Maven 3
A completely overhauled SSR dialog introduced autocompletion for templates and a simplified filters panel, replacing the complex "Edit Variables" popup.
Following the withdrawal of JEP 326 (Raw String Literals) from JDK 12, this update automatically migrates existing Java 12 projects to Java 11. Users can still access the experimental features by adjusting the project language level. It also added support for Multiline TODO comments
Comprehensive support for the latest Spring Boot features, including improved inspections and configuration management. Accessibility and UI
A standout addition for macOS and Linux, providing a low-overhead sampling profiler (Async profiler) to visualize execution stacks and flame graphs directly within the CPU Profiler tool window.
The update addressed a regression where the Rerun action for JavaEE server configurations failed to trigger an Update action, ensuring smoother deployment cycles for enterprise developers.