Compiling Groovy code is typically slower than compiling Java code, but in 14.1 we took a swing at speeding it up. First, we're now supporting Groovy-Eclipse compiler that handles Java and Groovy simultaneously, which brings a noticeable performance gain. So, if you're compiling your projects in Eclipse, you might want to give this new integration a try. Just go to the Java Compiler settings, s

Java annotations are awesome and helpful, but you need to add them by hand. Well, not anymore, because IntelliJ IDEA will do that for you in some quite important cases. Jars in your dependencies are stuffed with methods and sometimes it may be difficult to tell whether you can pass null there without blowing things up, or whether you should be ready to get null as a method result. If you're

Did you know how to quickly complete a static method call or a constant reference without writing the class name first? Just type some prefix and invoke Basic Code Completion (Ctrl+Space) twice (or Ctrl+Alt+Space once): There are two problems though: The entire project is searched and there might be just plain too many completely unrelated suggestions, and it's hard to search among them what y

As you know code completion in IntelliJ IDEA constantly evolves. Here's a few new features coming in IntelliJ IDEA 12: Middle matching Class Name Completion in Basic Completion Completion statistics in Productivity Guide Other minor improvements (more…)

Here I would like to tell you about some of the Groovy language support improvements available in IntelliJ IDEA 11.1. Unused Symbol Highlighting If a class, method or property is unused even if it is in fact public, you may notice it immediately with new unused symbol highlighting feature. (more…)

Sometimes you invoke an action and you don't get what you wanted immediately. In such cases it may help to invoke the action again by pressing the same shortcut. In basic code completion (Ctrl+Space) this will list non-imported classes: It works in similar way for smart-type and class name completions: In File Structure popup (Ctrl+F12) you will show inherited members with it: When introd

If you use completion autopopup in IntelliJ IDEA 11, you may have seen "n variants..." suggestions: This means there are two StringUtil classes available, neither of them is imported, and IDE can't choose which of them to put to the first place. When you choose such variant no new import statements will be added. The good side is that you won't get wrong imports after pressing space, dot or a b

With IntelliJ IDEA 10.5, you may press up to twice as less keys every day as you do now. Seriously! Here's how. The reason IDEs exist in the first place is that they make your life easier. In particular, they are able to generate code for you. An ideal IDE would do all the boring typing by itself, leaving you more time for thinking about the great software engineering problems you face. Unfortuna

IntelliJ IDEA is a great IDE for Java, Groovy, Flex, Python, Ruby and many other languages. The text editor with camel-hump completion, and version control support are so great that it may be hard to switch to another editor which may lack some useful features. So, when a need arises for me to code in a language that's not listed on the features page, I just teach IDEA some basics about that langu

Groovy's as keyword allows for some interesting features. In particular, it provides a convenient syntactic sugar for object creation: KeyAdapter listener = [         keyTyped: { e -> … },         keyReleased: { e -> … } ] as KeyAdapter Still in development, but already quite usable, there is Groovy++: a libr

Once I wrote about console folding for Groovy stacktraces. Naturally, many people wished similar things could work for other languages and frameworks. Long story short, there's now a settings page dedicated to the console folding. It provides a settings page where you may specify which console lines to fold: This functionality is available in IDEA 9.0.2 via Console Folding plugin. In IDEA X, it w

When you look at a typical Groovy stack trace, you usually see something like this: This is not terribly helpful, since there are only three lines from the actual source code. Everything else refers to Groovy's internals. From now on, though, reading Groovy stack traces will be much easier: