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

JRebel Standalone

Download Getting JRebel Standalone

  1. Download the JRebel Standalone ZIP.
  2. Unpack the archive to a folder of your choice.
  3. Next → Activation

Activation Getting your license up and running

  1. Find the jrebel-activate.jar file in the bin folder, right where you extracted JRebel. Run it!
  2. Fill out the form.
  3. Press Activate JRebel.
  4. Next → Startup configuration

Got a license?

Press I already 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.

Startup configuration Enabling JRebel agent for your server

  1. Add JRebel to the JVM startup arguments. Read more here.
  2. Next → Project configuration

Good to know

Head over to the JRebel Manual to read more about running servers with JRebel.

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 Generating rebel.xml

  1. JRebel requires an XML file to map your workspace to your deployed application.

Here is an example of a generated XML file:

<?xml version="1.0" encoding="UTF-8"?>
<application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.zeroturnaround.com" xsi:schemaLocation="http://www.zeroturnaround.com http://update.zeroturnaround.com/jrebel/rebel-2_1.xsd">
<classpath>
<dir name="C:/Users/user/workspace/spring-petclinic/target/classes">
</dir>
</classpath>
<web>
<link target="/">
<dir name="C:/Users/user/workspace/spring-petclinic/src/main/webapp">
</dir>
</link>
</web>
</application>

Learn more

Learn more about generating this XML file

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).
Learn more at the JRebel Learn Center.