How to Install Standalone Rebel.xml, Maven, and Gradle Plugins

For configuring Rebel XML configuration files, you must add the following agent path to the JVM command line.

They can be found on our documentation at the following link as shown.

To give you a visual, hey should look like this.

You will add your corresponding agent path depending on your operating system.

JRebel maps your project work space directly to a running application.

JRebel then monitors the changes you make to classes and resources and intelligently reflects them into your application.

In order for this to happen, JRebel needs to know where your classes and resources are. For this purpose, JRebel uses the Rebel dot XML configuration file, which can be shown just like this.

This XML file maps your deployed project back to your workspace.

This is obligatory when deploying your application as a WAR or EAR package.

One Rebel XML configuration file needs to be present per module.

This includes both web and EJB modules.

Specific details on each of these WAR, JAR, or EAR configurations can be found on our documentation.

When using a JRebel IDE plug in, it's recommended that the rebel XML file is generated using the IDE plugin.

We provide dedicated plugins for Maven and Gradle.

Generating Rebel XML using the dedicated Maven and Gradle plugins is intended for situations when generation using the IDE is not available.

The purpose of the JRebel maven plugin is to generate the rebel. XML file for your project during the Maven build.

In case of Maven projects, especially in case of multi-module projects, it is handy to use the JRebel Maven plugin for generating the Rebel XML configuration files for you.

The following snippet which you can see can be added to your parent palm .XML file.

The .XML configuration file will be generated for each individual sub module for your Maven project.

This will automatically generate the JRebel configuration file on every build.

If you just want to generate the Rebel .XML file, you would run a run a command such as the following:

mvn jebel:generate

The purpose of the JRebel Gradle plug-in is to generate the Rebel .XML file for a project during the Gradle build.

When using Gradle two point one or newer, add the following snippet to the top of your build.gradle script, as you can see right here.

The plugin provides a new task called generate Rebel that by default depends on the process resources phase.

For more fine tuned control, it can be changed to only run before certain tasks.

For example, only before building a warad artifact.

You can run the following command: war.depends on and the new "generateRebel" rule.

In most cases, this is all you need to do.

The plugin should be able to read the locations of your classes and resources from Gradle's project model and put them into your rebel.XML