Have you ever seen a project with no unused symbols? If so, you are really lucky! Jokes aside, finding unused code is difficult because of things like dependency injection, reflection, and countless frameworks. Luckily we have IntelliJ IDEA that provides instance editor highlighting and batch inspection that are a great aid in this task. Unfortunately, sometimes static information is not enough to detect that code is implicitly used by a framework or called through reflection, or your project is a library and all public methods are therefore implicitly used. To make the inspection more flexibl

If you've already given a shot to a recent IntelliJ IDEA 15 EAP build, you might have noticed changes in the UI for running tests. Today, as we've released a new EAP build with even more bugfixes and enhancements, the new UI is ready for preview. IntelliJ IDEA supports a variety of test frameworks: the first was JUnit, then TestNG (developed initially by Hani and Mark) following by non-Java frameworks for Ruby, PHP, JavaScript, etc. The Java frameworks used to have one UI, and the frameworks added later introduced another one. Maintaining different UIs (as well fixing the same bugs in sever

IntelliJ IDEA already has impressive code generation capabilities: it can create getters and setters, equals(), hashCode(), toString(), and other methods, some of which are really simple to generate, and some are quite not. That's why the toString() method generator included the support for Velocity templates that could be modified and tailored to your needs. In IntelliJ IDEA 14.1 we're extending this support to all other generated methods. To fully support this new feature, the Template Editor has been upgraded with complete Velocity coding assistance. Note that this particul

  Sometimes it is convenient to work with all methods in a call hierarchy in the same way: add or remove a parameter throughout the entire call hierarchy, make the whole hierarchy static, or delete the whole call hierarchy completely. IntelliJ IDEA 14.1 makes this process simpler. class CallHierarchySample { private void foo() { bar();} private void bar() { baz();} private void baz() { } } Change Signature It's probably not a very well-known feature that it's possible (since IntelliJ IDEA 4?) to add a parameter or an exception to all methods in the call hier

              Extract Surrounding Method: You have two methods that contain nearly identical code. The variance is in the middle of the method. Extract the duplication into a method that accepts a block and yields back to the caller to execute the unique code. Jay Fields, Shane Harvie In Java, if we want to replace a block inside a method, the block should have a ‘known shape’ for surrounding code to be able to call it. Let’s perform a code transformation with the following example, step by step: private void foo() { int i = 0; <selection>System.out.println(i * i);</selecti

<Extract method refactoring> turns a fragment into a method whose name explains the purpose of the method. Martin Fowler When we select a block of code, IntelliJ IDEA’s data flow analysis engine is able to deduce all local variables and parameters that are used inside, but are declared outside of it. These variables form the initial set from which a parameter list of the extracted method is be constructed: int i = 0; <selection>System.out.println(i);</selection> Initial set is {i}, and the extracted method will have a signature such as newMethod(int i) . So far, so good

This is the third part of the JavaFX 2 serie about the new features coming in IntelliJ IDEA 12.1. Today we would like to show how you can prepare your application deployment bundles. Since the last two posts we have updated the project wizard so when you create a project it comes with an already configured artifact. If you accept to create a project and open File → Project Structure → Artifacts, you will see a configured artifact of JavaFx Application type. (more…)

This is the second part of the serie about Java FX 2 support in the upcoming IntelliJ IDEA 12.1. Today we would show some features dedicated to help you to skin your JavaFX application with CSS. We would use the same sample application we were using in the previous post. As you know JavaFX allows to configure stylesheets for nodes in your .fxml. IntelliJ IDEA helps to complete existing .css files: You may rename, move, etc your .css file, the reference would be updated accordingly. If you deside to add one more stylesheet and want to convert attribute value to subtag, the IDE would also hel

Over the last year we have been asked to add support for JavaFX 2 quite frequently. Today we are pleased to announce the first preview of the JavaFX 2 plugin for IntelliJ IDEA 12.1. Having Java 7 installed you may create a new demo project based on JavaFX Application template: (more…)

As you might know IntelliJ IDEA 12 will bring support for new features of Java 8 language. Though this is still in progress, you can try some of these features now in IntelliJ IDEA 12 EAP. Here we would like to provide some details on method and constructor refereces support. IntelliJ IDEA as always provides a way to transform existing code to use new features. Dedicated inspection finds and highlights anonymous types which can be replaced with a method reference. After you apply provided quick-fix, it gets just a line of code. There is also another inspection that checks if a lambda e

IntelliJ IDEA 11.1 introduces a new way of browsing the gathered coverage information through a dedicated Coverage View. This view aggregates the coverage details over a configured scope in one place. It provides ability to sort data by coverage percentage, what can be used for detection of code which is not enough covered by tests. As always quick navigation, scroll from/to source, flatten packages mode are available in Coverage View for an easy work with the results. It also allows generating HTML report right from the view. Please note, that the view is also available for Python, Ruby a

Sometimes you have an abstract test class with test methods where the inheritors set up different environment. As it is impossible to run an abstract class you had to enumerate inheritors manually, choose corresponding methods and run these methods one by one. Now (since IntelliJ IDEA 11.1) it is possible to run tests right from the abstract base class and simply choose inheritors from the popup. This works for JUnit and for TestNG tests.