Installing the JRebel plugin
- Download the JRebel plugin archive.
- Open Help > Check for Updates and select Install From Local File.
- Browse to the downloaded ZIP and press Next.
Using JDeveloper 11g R1? Download this plugin.
Did this work?
If the installation was a success, your IDE will restart.
Getting a license
- Open Tools > Preferences.
- Find JRebel. Press JRebel Config Center.
- Open the Activation tab on the left and select your desired option.
Get JRebel Trial
Head on over to JRebel Trial and fill out the form to get your personal trial license.
Got a license?
- Choose license file from the disk. Point to your
jrebel.licfile. You get this file via email when you purchase JRebel. - Activation code. Paste your activation code if you have one already.
- Connect to ZeroTurnaround License Management or an on-premises License Server. Enter your team URL and email. You get the team URL from your network administrator.
Mapping your workspace to the deployed application
- Right-click your project and select Project Properties > JRebel panel.
- Press Generate now!
- Redeploy your application (or restart your standalone application)!
Didn't work?
- Using Maven? Use the JRebel Maven plugin to generate
rebel.xml. JRebel Maven instructions. - Running Gradle? Use the JRebel Gradle plugin to generate
rebel.xml. JRebel Gradle instructions. - Need to tweak your
rebel.xml? JRebel rebel.xml reference manual has the answers.
Did this work?
When building your application, rebel.xml should be included within the application archive.
- In case of JAR files,
rebel.xmlshould be included in the root folder. - When working with WAR files, the
rebel.xmlshould be located within the WEB-INF/classes folder. - EAR files require a
rebel.xmlfor each internal EAR module (that means JARs and WARs).
Enabling JRebel for your JDeveloper
- Press the JRebel button on the toolbar. This will enable JRebel throughout JDeveloper.
Good to know
How to start JRebel from a command line.
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: #############################################################
JRebel in action
- Restart your application server or Java application.
- Change something in the application code.
- Open Build > and select Make All.
- Refresh the application in the browser to see the changes!
Why do this?
JRebel does not compile classes, it only reloads them. JDeveloper doesn’t compile changed classes automatically. This means that you will have to manually make your project after changing Java code.
Avoid rebuilding your project when the application is running with JRebel. JRebel uses file timestamps to check if they have been modified. Reloading all the resources in a large application will have an impact on performance.