JRebel Quick Start

Follow this quide to get JRebel up and running.
Pick your IDE on the right.

Watch it in action

JRebel Quick Start

IntelliJ IDEA

Installation Installing the JRebel plugin

  1. Access Settings (Preferences on Mac OS). Select Plugins.
  2. Press Browse Repositories.
  3. Find JRebel. Press Install plugin.
  4. Next → Activation

Didn't work?

The plugin can also be downloaded as a ZIP archive from http://plugins.jetbrains.com/plugin/?id=4441. Once downloaded, open Plugins and press Install plugin from disk. Browse to the downloaded file and follow the prompts.

Did this work?

If the installation was a success, your IDE will restart. After the restart, JRebel will alert you via a notification.

Activation Getting a license

  1. Open Help > JRebel > Activation.
  2. Fill out the form.
  3. Press Activate JRebel.
  4. Next → Startup configuration

Got a license?

Press I already have a license in the activation window.
  • Activation code. Paste your activation code if you have one already.
  • License file from the hard drive. Point to your jrebel.lic file. You get this file via email when you purchase JRebel.
  • Connect to License Server. Enter your Group URL and email. You get the Group URL from your network administrator.

Did this work?

JRebel will let you know that your license is activated via a notification.

Startup configuration Adding JRebel agent to your server or standalone application

  1. Press the jrebel-ide-icon Run with JRebel button on the toolbar to run your application with JRebel enabled.
  2. Next → Project configuration

Good to know

Did this work?

When successful, you will see the JRebel banner in the console right at server startup. This is what the JRebel banner should look like:
2016-11-15 12:19:20 JRebel:  #############################################################
2016-11-15 12:19:20 JRebel:  
2016-11-15 12:19:20 JRebel:  JRebel Agent 7.0.0 (201611081555)
2016-11-15 12:19:20 JRebel:  (c) Copyright ZeroTurnaround AS, Estonia, Tartu.
2016-11-15 12:19:20 JRebel:  
2016-11-15 12:19:20 JRebel:  Over the last 1 days JRebel prevented
2016-11-15 12:19:20 JRebel:  at least 0 redeploys/restarts saving you about 0 hours.
2016-11-15 12:19:20 JRebel:  
2016-11-15 12:19:20 JRebel:  Licensed to ZeroTurnaround.
2016-11-15 12:19:20 JRebel:  
2016-11-15 12:19:20 JRebel:  #############################################################

Project configuration Mapping your workspace to the deployed application

  1. Open View > Tool Windows > JRebel panel. The JRebel Modules window opens.
  2. Enable JRebel for the desired modules by selecting the column checkboxes.
  3. Redeploy your application!
  4. Next → Reload your code

Didn't work?

Did this work?

When building your application, rebel.xml should be included within the application archive.
  • In case of JAR files, rebel.xml should be included in the root folder.
  • When working with WAR files, the rebel.xml should be located within the WEB-INF/classes folder.
  • EAR files require a rebel.xml for each internal EAR module (that means JARs and WARs).

Reload your code JRebel in action

  1. Restart your Java application using jrebel-ide-icon Run with JRebel.
  2. Change something in the application code.
  3. Use Build > Make Project command to compile classes and update your application.
  4. Refresh the application in the browser to see the changes!

Why do this?

JRebel relies upon your IDE to do the compiling. JRebel reloads your compiled .class files and not your .java files. When you change code, JRebel pushes the changed classes and resources to the server without redeploying.
Learn more at the JRebel documentation.