Intellij on JAVAPRO International

Maintaining the IntelliJ “Save Actions” Plugin: A Community Effort to Keep Development Tools Up to Date

Wed, 12 Nov 2025 12:00:01 +0000

For many developers working with IntelliJ IDEA, the “Save Actions” plugin has long been a trusted companion for maintaining consistent and clean codebases. By automatically performing configurable actions on file save—such as optimizing imports, reformatting code, rearranging members, or applying small quick fixes—the plugin helps ensure that projects stay uniform across entire teams.

After the original development of “Save Actions” came to a halt several years ago, the plugin risked falling out of compatibility with newer IntelliJ versions. To prevent this, XDEV Software stepped in as the dedicated maintainer and continues to provide updates and maintenance releases through the JetBrains Marketplace. The goal has remained simple: to keep the plugin functional, compatible, and stable for the growing developer community that relies on it.

Japo: The Ultimate Search Engine for Java Annotations

Thu, 21 Aug 2025 07:00:01 +0000

In the evolving landscape of Java development, annotations play a critical role in simplifying code, enhancing readability, and enabling powerful framework capabilities. Yet, finding detailed, accurate, and consolidated information about Java annotations has long been a challenge for developers. JAPO (Java Annotations Repo) is the game-changing solution addressing this gap. Offering a feature-rich search engine, JAPO enables Java developers to explore annotations, Maven artifacts, and much more with unparalleled ease.

1 Billion RECORD CHallenge - AI Style

Thu, 07 Nov 2024 10:05:34 +0000

Previously …

I recently wrote about my experiences with getting AI coding tools to find bugs and write tests. I picked five different tools. The selection criteria were simple - free or trial with no credit card needed. I chose three tools designed to help developers and two general-purpose LLMs.

I gave them a 1000-line Java program and asked them to do three things.

Add Javadoc to explain what the code did
Analyse the code for bugs and design weaknesses
Create Junit testcases that would provide reasonable code coverage.

The results were disappointing but, in hindsight, predictable. Overall, the tools were better at creating documentation than finding bugs and, apart from one, were pretty poor at writing test cases.