Installing and Configuring JRebel/XRebel for Hot Deployment in IntelliJ IDEA

Hello everyone, I am Chen.

IDEA does not support hot deployment natively, so most code or configuration changes require a server restart.

JRebel is a JVM plugin that lets Java developers see code changes instantly without redeploying, skipping build and deployment steps and saving a lot of time.

The best current solution for hot deployment in IDEA is to install JRebel.

XRebel is an interactive web‑application analyzer that shows warnings in the browser when problems are detected and monitors performance metrics in real time.

Official documentation: https://manuals.jrebel.com/jrebel/index.html

Installing JRebel/XRebel

1. Search for JRebel in the IDEA plugin repository and install the bundled plugins.

2. The plugin is commercial; you need to activate it.

Navigate to help->JRebel->Activation

Server address: https://jrebel.qekang.com/{GUID}

Generate a GUID from an online GUID service.

Combine the server address and GUID and paste into the Team URL field.

Click CHANGE LICENSE .

After these steps JRebel is activated.

Configuring JRebel

1. Set offline work mode by clicking WORK OFFLINE .

You can also adjust JRebel's auto‑refresh interval.

2. Enable automatic compilation in IDEA (usually enabled by default).

In advanced settings check Allow auto‑make… .

Hot Deploying a Project

1. Open JRebel and select the service you want to hot‑deploy.

2. In a Spring Boot project, choose the classes and resources to update.

3. Launch the project with JRebel+XRebel (or only JRebel if you only need hot deployment) instead of the native run configuration.

4. When multiple micro‑services exist, select all services in the service list and start them with JRebel.

Now, whenever code changes in any service, press Ctrl+Shift+F9 ; JRebel detects the change, reloads the class, and you can continue development without restarting the server.

Using XRebel for Performance Analysis

1. Access XRebel

After the project starts, open http://localhost:8080/xrebel (replace with your server address).

2. Activate XRebel

Activation is the same as for JRebel.

3. Features

Capture runtime exceptions.

Observe each call in detail with step‑by‑step execution times.

View detailed source code execution flow for each step.

See SQL execution time and formatted statements for database operations.

Access detailed system logs and download them locally.

Supports both single‑node and distributed micro‑service environments.

Summary

The above introduces JRebel and XRebel; after mastering them you no longer need to restart the server for every bug fix.

Source: blog.csdn.net/qq_53263107/article/details/123984383

Final Note (Please Support)

If this article helped you, please like, watch, share, and bookmark; your support keeps me going.

My knowledge community offers premium content for a small fee; see the original post for details.

Follow the public account "Code Monkey Technical Column" for more resources and join the discussion group.