As we announced some time ago, we are discontinuing support for ClearCase and Visual SourceSafe as of the 2017.3 release. This implies several things: Visual SourceSafe Integration plugin has being unbundled for some time already and starting from the latest EAP, ClearCase plugin is also removed from the standard package. Since we do not plan any further development of the plugins, we will close all YouTrack reports for these plugins as of the 2017.3 release. Plugins are now compatible with the Community Edition and are published in the JetBrains plugin repository: https://plugin

We've just published a new IntelliJ IDEA 2017.2 EAP build, in which you'll find some quite interesting new features. (more…)

In this week's Git video, Gary and I look at how you can Annotate your code to see who made which changes.  We also show how you can use this information to understand a bit more about the context of a particular change.

In this week's Git questions we take a look at a simple but rather important step when you're working on a GitHub Open Source project - how do you get started? In the video, Gary and I demonstrate how to fork and clone a project (I chose some Spring example code and Gary chose a JavaScript framework) and how to set up additional remotes so that you can easily keep your fork up-to-date as per our last video. This time Gary's demonstrating the functionality in WebStorm while I stick with IntelliJ IDEA, as usual the features we demonstrate are common to all the IntelliJ Platform IDEs.

Carrying on our series of Git Questions, this week Gary Hockin (PhpStorm Advocate) and I look at the question: how do I make sure my GitHub fork is up to date when the open source project it forked has moved on? GitHub's help does, of course, cover this question. But not everyone is comfortable working from the command line, and even those who are, sometimes prefer to use the IDE if they're already working in it. This video shows an answer to this question which uses Git's fetch, pull and push from within IntelliJ IDEA.

We regularly get questions about how to achieve a particular thing - as developers there are parts of our workflow which trip us up, that our tools can help us with if we understand how.  So we've decided to start answering these real world questions with videos showing what to do. The first video features me, Trisha Gee (Developer Advocate for IntelliJ IDEA) and Gary Hockin (Developer Advocate for PhpStorm) answering the question "How do I switch branches without losing the code I was working on?". Through frequent battles with Git I have learnt there's always more than one way to do thing

In one of her recent articles, Trisha Gee wrote about refactoring to Java 8. Among many great tips about Java 8, the article also showed how IntelliJ IDEA helps write correct and idiomatic Java 8. With IntelliJ IDEA 2016.3, we've gone further and extended our existing inspections to support non-trivial cases. (more…)

As you may know in IntelliJ IDEA 2016.2 EAP we've finally fixed a very annoying issue that didn't allow to commit case-only renames in IntelliJ IDEA. For a number of reasons, the solution was not so trivial, we decided to share some of its implementation details with you. When you are on a case-sensitive file system (Linux), case-only renames are just like any other renames, so you're all good. However, when the file system you're using is case-insensitive (like Windows or Mac), some of many Git commands will treat changing the file name case as a change, while others won't. Because of that

A fresh IntelliJ IDEA 2016.2 EAP build is out and ready to test. Besides usual bugfixes it brings improvements to the Git/Mercurial Log viewer. The Log viewer now loads in the background on every change (a commit, fetch, rebase, etc). As a result, it's always ready when you open it. Also, we've reworked the way we show the loading progress. Now, when refreshing, there's a thin stripe shown under the toolbar. We hope you'll enjoy these minor improvements. If you experience any problems, feel free to file issues directly to the issue tracker. Develop with Pleasure!

A fresh EAP build for IntelliJ IDEA 2016.2 is out and, being a good EAP build that it is, has something new for you to try: General A new inspection that warns you when you instantiate new objects inside equals, hashCode, compareTo or Comparator.compare methods. This helps to avoid significant performance problems when, for example, objects of classes with such constructs are added to Set or Map, where these methods will be frequently invoked. Coding assistance for Regex has been extended with better error reporting and added code completion for named group references. T

Great news, everyone! A fresh weekly IntelliJ IDEA 16 EAP is out and ready, packed with bugfixes and new features as usual. The noticeable changes affect the debugger, VCS integrations, and user interface. Debugger Now when debugging a Java application, you can use Groovy expressions with Evaluate Expression and Watches. Previously you could do that only when debugging Groovy code. This is good because Groovy expressions are much shorter and more expressive (especially when you work with collections.) This feature requires a Groovy runtime library in the classpath. Also, we've

Every week we publish a fresh IntelliJ IDEA 16 EAP. Today's build, among bugfixes that address issues you reported, brings a few improvements to Git integration and IntelliJ IDEA heart, the code editor. Move elements right and left We already have a way to move code statements up and down: Ctrl + Shift + Up/Down (Cmd + Shift + Up/Down for OS X.) They come in handy when you're rearranging code statements. Sometimes, however, it might be useful to move them left or right (when you're, for example, changing the order of attributes of an XML element, method parameters, or elements in an arra