Remote servers feature upgraded in JRebel for IntelliJ 6.3.2

Great news everybody! We have reimplemented the remote servers feature in JRebel for IntelliJ 6.3.2. We have made it much more powerful as well as easier to configure.

The remote servers view

First of all, we have introduced a Remote servers view into the global settings. You can find this by opening Settings > JRebel > Remote servers. From here on out, this will be the central place to manage all your remote server connections. Through this UI, you are able to add, edit, remove, enable and disable JRebel remote servers — where you can then update code with JRebel.

The idea is that these servers are reusable for all your projects. Enable the ones you want to work with at any given time. If you then synchronize your changes with JRebel (by clicking the Synchronize button or by enabling Synchronize on build), all the deployments of the modified projects will be updated for the servers you have enabled.

You no longer need to define remote server URLs one-by-one for each of your remote projects (which will be a big win if you happen to work with a whole bunch of projects).

Changes to JRebel project settings

Since the remote server settings are now managed centrally in the global configuration, JRebel project settings look a lot more simple. You just have to decide whether you want to enable remote server support for a particular project. The project will then be synchronized to all remote servers that are enabled and to which this project has been deployed to.

Notice that you can also turn on JRebel or JRebel’s remote server support for a project via the JRebel Modules tool window. It does the exact same thing as the radio selector in the project settings dialog.


Automatic migration for your existing configuration

With the plugin upgrade to JRebel 6.3.2 or later, we perform automatic migration for your old remote servers configuration — to match with the new implementation.

Let us assume that your project was set up with the following configuration in an older version of JRebel for IntelliJ:

When upgrading to JRebel 6.3.2 or newer, the migration automatically converts this project setup to a remote server with the URL http://myserver:8080/ (without the application context path, since this is no longer required). The project settings will be automatically switched to Use remote servers. The migration is completed automatically and you are then good to continue working with the new JRebel remote implementation!

Remote servers log

Last — but not least — we have introduced a log console for all JRebel remote server activities. This is where you can find all the details about your remote server transactions, in case you should need them (especially if something went wrong). This way we can stop bothering you with those details in the events log and in countless IDE notifications.


This console pops up automatically during remote server transactions. You can open it manually by clicking the JRebel Remote server log at the bottom right status bar of IntelliJ IDEA.