JetBrains IntelliJ IDEA Blog

The most exciting news for me is that now in forthcoming IntelliJ IDEA 11, we show Git revisions graph!

Now that IntelliJ IDEA can visualize commits links, we’ve added context actions to tag a commit, create (and checkout) new branch, and checkout a selected revision.

I want to specifically mention the highlight actions — now you can see what commits are in “ancestors subgraph” for a selected commit. By default, IntelliJ IDEA shows HEAD subgraph, i.e. you see what commits you have in your working tree now.

It is really convenient when you are checking what commits went into some tag (or branch).

To find any commit in git log (in already shown part), use the new “Goto Commit” action — type commit hash, or description fragment, or branch or tag name, and be navigated to it.

And, finally — when browsing history, sometimes you work with a set of commits and need to track this set.

Now you can mark commits by simply pressing Space and they get stared.

In IntelliJ IDEA 10.5 we’ve improved setting up your Perforce server connection and connection state diagnostics.

Configuring connections

If you are using P4CONFIG files for configuration, IntelliJ IDEA shows what config files it has found and what other default settings are used. This way you can be sure that your P4CONFIG files are found and taken into account.

Use the ‘Test Connection’ button in ‘Settings | Version Control | VCSs | Perforce’ to see this information.

Moreover, in case you specified a wrong client workspace and your project roots do not match with the workspace roots, you are also clearly prompted:

If you are not authenticated to the server or the authentication ticket has expired, you will be notified accordingly:

Offline mode

Once Perforce server becomes unavailable, IntelliJ IDEA switches to the offline mode automatically and displays an offline notification.

In the offline mode, you can continue working locally as usual, file checkouts are remembered by IntelliJ IDEA to be further re-played. When going online IntelliJ IDEA requires that you authenticate on the server and the ticket is not expired. This is important to re-play you offline edits properly.

It is snowing outside our office but it is getting hotter and hotter inside. Guess why? That’s right, releases are getting nearer. RubyMine team did theirs yesterday. IntelliJ IDEA 10 is close enough too.

Indeed, we’ve just published IntelliJ IDEA 10 Release Candidate!

One major thing we pushed to this build is a significantly reworked Git log view (see screenshot below).
There’s also a number of other Git-related changes plus many stabilizing fixes throughout the IDE. See the complete list in this build release notes.

So, if you have some feedback for us, please speak now! We are listening as carefully as we push our changes now!

Stay tuned for more releases from JetBrains and for IntelliJ IDEA 10 announcement soon!

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)

If you’re a lucky owner of IntelliJ IDEA 9 Ultimate Edition, you’ll be surprised to find a new action in VCS History panel: view all changes made in commit in a single dialog. This feature makes it simpler to understand what a commit author made in his change.

To start using this feature, invoke Show History action for any file, then select revision you’d like to investigate, and then click UML icon (or press Control+Shift+D).

This opens the following diff dialog:

As you can see, 3 changes are made in layout.properties, Rounded interface and RoundedButton class. By default, green color marks what was added, blue is for changed, and gray, guess what — deleted. Well, what else can we see here? RoundedButton class doesn’t extend JComponent and does not implement ButtonModel interface anymore, but instead it extends AbstractButton class and implements MouseListener and KeyListener interfaces. Also, author has changed method paint and removed method isPressed. Interface Rounded was added from scratch and some properties were modified, added and removed in layout.properties file. Double click on a node shows standard diff dialog.

You will be able to enjoy this UML-like Diff Tool in next EAPs and also in the nearest IntelliJ IDEA 9 update.

In the upcoming Maia EAP you will find a slightly different Commit Changes dialog.

• Automatic use of JobView filter on search results.
• Support for Perforce native search query syntax (in an example below we’re looking for Job in any field)

In Maia, you will be able to use the Ctrl+D shortcut in the update info tab to see which local files were changed after you perform update from repository.

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.