JetBrains IntelliJ IDEA Blog

As for me, after a few years of working in a huge project inside a big team, I became concerned about accidentally breaking the project.

That’s why every time I commit something, I double-check my changes.

In the forthcoming IntelliJ IDEA 11 EAP, I have a special “digest” changes presentation for that!

It helps me in my last pre-commit check immediately inside the commit dialog:

And I also use it all the time when coding, to recall my changes:

NB: to see the digest of changes in Changes | Local, use the new “Change Details” toolbar button.

To tell the truth, even when I was in the middle of this “digest” changes feature, I simply couldn’t live without it, so I compiled a build of IntelliJ IDEA for myself and used digest view while developing the digest view!

IntelliJ IDEA 11 EAP is to be announced any day now. Stay tuned!

There’s been a number of new things we’ve added in IntelliJ IDEA 10.5 related to version control support. You can try them already in a latest EAP build. And here’s a quick overview.

Do not forget things… TODO!

Now you can easily ensure you haven’t forgotten to implement a method, and double-check the important places in your code before commit. Just mark those places in code with TODO.

IntelliJ IDEA’s new “Check TODO” before commit inspection will notify about all new and edited TODO items.

It will also confirm about TODO items in the changed fragments (in case they are not actual any more).

You can use TODO filter with this inspection — if you want to pay attention only to TODO items of a special kind.

You can further review TODO items in the changed lines:

Import patches into IntelliJ IDEA shelf

You can now import a patch into shelf.

It is quite useful when you review someone’s code and use patches for communication.

Later, you can unshelve it using the new detailed Unshelve… action, which opens a dialog similar to ‘Apply Patch’ and allows setting any bases for the patch parts (in case some files or directories had moved since then).

You can also import patches directly from the Apply Patch dialog.

Subversion. GNOME Keyring support

GNOME Keyring support has been implemented by svnkit, so you can use it in IntelliJ IDEA now.

As svnkit folks say, it is in experimental phase, and a special JVM key should be used to enable it. So, please read the details.

This is it for now. Let us know what you think.

And make sure you are using the latest IntelliJ IDEA 10.5 EAP build when you get to try these and other new features.

How many times you wished you could edit your last VCS commit comment to correct a misspelling?

Now you will notice such mistakes because IntelliJ IDEA 10 checks the spelling in the comment field.

And it not just spellchecks the text, it runs the Spelling inspection on it and uses your custom dictionary too. Hit Alt+Enter/⌥↩ on an underlined word and fix it as you normally fix things in IntelliJ IDEA code editor.

Spellchecker is also enabled in other dialogs throughout the IDE, e.g. Search/Replace dialog.

Try IntelliJ IDEA X EAP and let us know your impressions.

When diving into code details, the most common question would often be:

- Why does this line stay here?

When annotation doesn’t give the answer, jump into the change contents in one click:

(coming in next IntelliJ IDEA EAP)

When you have changes in several files or classes and want to see what they affect, you typically use the Changes tab and then Show Diff action for every affected file or class. In Maia, you will be able to see the complete picture at once, via UML Class Diagram. It is improved to allow viewing and highlighting of changed and removed classes, methods, fields and so on when you press Ctrl+Alt+Shift+D.