New IntelliJ IDEA 11.1.5 EAP build 117.1006 is available for download.
The build contains several important fixes for Subversion VCS support related mostly to SVNKit library: checksum mismatch and BUSY exception problem.
The full list of changes can be found in Release Notes.
Please feel free to share your feedback and report bugs in our issue tracker.
Develop with Pleasure!
In the new EAP we deliver performance and memory usage improvements together with a bunch of Subversion fixes.
We especially would mention IDEA-85279 (which introduces better connection pool) and
IDEA-75800 (the problem with merge and branch point search had been solved).
You can find the complete list of changes in the build. Download it or upgrade from within the IDE using the “Check for updates” feature.
New IntelliJ IDEA 11.1 EAP build (116.32) is available with Subversion 1.7 support finally built in. Here are some details on the current implementation.
We don’t perform automatic upgrade of your working copies to version 1.7, you can easily do it manually (Changes | Subversion Working Copies | Change).
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.
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!
In IntelliJ IDEA 10.5 we’ve improved setting up your Perforce server connection and connection state diagnostics.
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:
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.
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.
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:
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.
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.
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)
Feature branches have simple life cycle, they usually consume trunk changes and are merged back into trunk after the work is completed.
In IntelliJ IDEA 9.0.3 EAP, take all trunk changes into feature branch and reintegrate back into trunk using new “Merge from…” action:
You can merge all changes in one shot or select a subset of them. Changelist with merged changes is created and offered for commit.
In the upcoming Maia EAP you will find a slightly different Commit Changes dialog.
Tweets about IntelliJ IDEA
