The JRebel plugin for IntelliJ IDEA includes the JRebel agent and helps you to automatically generate the JRebel configuration. It enables JRebel for applications and servers with a single click and improves the debugging support in the IDE.
Tip
Installing JRebel for the first time? Check out this handy Quick Start.
4、设置JRebel Agent 5、项目中添加(或删除)JRebel支持： 1）添加JRebel：选择项目，鼠标右键，再选择如下菜单即可(添加JRebel支持后项目src目录下会多出一个rebel.xml的文件) 2）删除JRebel：选择项目，鼠标右键，再选择如下菜单即可. Because I have installed DCEVM using 'sudo apt install openjdk-11-jre-dcevm' in Ubuntu 19.04 and also the plugin in IntelliJ Ultimate 2019.1.3. If installing 'Hotswap agent' let alone do the job of JRebel, what's the use of DCEVM!? – user10995419 Aug 8 '19 at 1:38. With an upcoming release (post 6.4.6) of JRebel, the JRebel 6 agent will not instrument dynatrace classes anymore. Please note that the JRebel legacy agent does work without any known issues. NAM 2019 SP4 is available. Check updated libraries and support added in the latest NAM service pack. Nuxeo and JRebel hot deployment Hello, I have a question about nuxeo-cap-5.5-tomcat and JRebel. Does anybody try to do hot deployment with this tool and if yes what are the configurations, because I am not sure that I set the configurations on the right way. The makers chose not to release the film in Pakistan due to the 2019 Pulwama attack. The film was made available as VOD on Prime Video in June 2019. Critical response. On Rotten Tomatoes, the film had scored 25% based on 8 reviews with an average rating of 4.6/10.
Note
JRebel for IntelliJ IDEA supports version 2016.x or newer.
Using IntelliJ IDEA version 12.x or older? Please download JRebel 6.2.5 for IntelliJ IDEA.
Using IntelliJ IDEA version 13.x? Please download JRebel 2018.1.2 for IntelliJ IDEA.
Using IntelliJ IDEA versions 14.x or 15.x? Please download JRebel 2020.2.3 for IntelliJ IDEA.
Installation¶
Install from plugin repositories¶
To install the JRebel Plugin for IntelliJ IDEA via IntelliJ repositories, follow these steps:
Open the IntelliJ IDEA Settings… dialog. Select Plugins from the sections menu.
Press Browse plugin repositories… and locate the JRebel plugin.
Press Install plugin to download and install the JRebel plugin for IntelliJ IDEA.
Tip
IntelliJ IDEA might warn you that JRebel plugin depends on WebSphere and WebLogic plugins that might be disabled or not available in case of IntelliJ IDEA Community Edition. This is totally fine. These dependencies are optional and you can either accept or decline the enabling of the corresponding plugins.
IntelliJ will ask you to restart in order to complete the plugin installation. Make it so.
Install from ZIP archive¶
The plugin can be acquired also as a ZIP archive. All the released versions of the plugin are hosted at http://plugins.jetbrains.com/plugin/?id=4441.
To install the plugin from the ZIP archive, follow these steps:
Download the latest version of the plugin from http://plugins.jetbrains.com/plugin/?id=4441.
Once downloaded, open the IntelliJ IDEA Settings… dialog. Select Plugins from the sections menu. Press Install plugin from disk… to locate the plugin.
Browse to the location of the downloaded ZIP archive.
Press OK to confirm the installation. The IDE will ask you to restart in order to complete the plugin installation. Restart your IDE.
Upgrading to release version from nightly build¶
Note
Following this procedure is only required for IntelliJ IDEA 13 and IntelliJ IDEA 14 users.
Access Settings (Preferences on Mac OS). Select Plugins.
Locate JRebel for IntelliJ.
Right-click the plugin name and select Uninstall.
Once done, reinstall the release version of JRebel for IntelliJ:
Access Settings (Preferences on Mac OS). Select Plugins.
Press Browse Repositories.
Find JRebel. Press Install.
Activation¶
Following the installation, you probably won't have a license yet. Once your IDE restarts, the JRebel plugin will notify you about this. This happens via a popup notification:
Click the link in this popup. The JRebel activation window will open. If you closed the popup, you can also open this window from Help > JRebel > Activation.
This window contains two tabs: Try JRebel for FREE and I already have a license.
Try JRebel for FREE¶
To start your 14-day free JRebel Trial, fill out this form, select I agree with the terms & conditions of theJRebel License Agreement and press Activate JRebel. It's as easy as that!
I already have a license¶
Open this tab if you already have a JRebel license. You can select one of three activation options:
Activation code – Select this and paste your trial activation code in the text field. Press Activate JRebel to activate using the activation code.
Choose license file from the hard drive (jrebel.lic) – Select this option if you bought a license. We will send you a
jrebel.liclicense file using email. Press Browse and locate yourjrebel.liclicense file on the hard drive. Next, press Activate JRebel to activate using the license file.Connect to License Server – Select this option if your network administrator supplies you with a License Server Group URL. The Group URL is a unique URL, consisting of the License Server address and a unique key. Paste the Group URL into the first field and input your email address into the second. Press Activate JRebel when done to activate using the License Server. JRebel 6 requires License Server 3 or newer for activation.
If everything went according to plan, you should now have a fully functional JRebel installed!
Project configuration¶
The only required configuration file is rebel.xml. This is used by JRebel to map the running application to the workspace. The good news is that IDE plugin can automate this configuration for you.
Right-click on the project node in the Project View and select JRebel > rebel.xml.
A dedicated configuration file should be generated for every module in the project. For more information please see the 'Application configuration' chapter.
From this context menu you can also open the module configuration settings. To do this, right-click the desired module and select JRebel > Configure module.
Jrebel 2019 1 4 Release
Note
IntelliJ IDEA does not compile classes on save by default. Press Ctrl+Shift+F9 to compile the current file, module or package (you can also find this command via Build > Make Project).
Once you have generated
rebel.xml, you need to redeploy your application to the server for the configuration to take effect.
If you would like to make modifications to the configuration file, please see the full reference for rebel.xml file format.
Note that when using either Maven or Gradle for your project, you might consider using the respective plugin for generating rebel.xml (and not the IDE plugin). For more information, please refer to either Maven plugin or Gradle plugin.
Tool window¶
The JRebel tool window provides an overview of JRebel configurations for the active project. This tool window displays a flat list of modules of the project. From here it is possible to quickly enable JRebel configuration for a particular module.
By selecting the checkbox next to the module name, you will generate the rebel.xml configuration file that will be placed into the source tree of the project. For Maven projects it will be placed into src/main/resources so that it will be picked up automatically during the build.
Note
Please note that rebel.xml should be deployed to the application container with the application.
Using relative paths in rebel.xml¶
Refer here for instructions. This is the way to go if you want to commit your rebel.xml and share the configuration with the whole team.
Server startup¶
The JRebel plugin for IntelliJ IDEA includes dedicated launch buttons. These buttons are located on the main toolbar and on the navigation toolbar by default. You can also find these commands via the Run menu.
The first button launches the container with JRebel. The second button launches the container with JRebel in debug mode.
By launching the process from one of these buttons, the JRebel plugin will automatically add the appropriate command line parameters.
External servers and remote servers¶
When launching the application server from a command line or using a remote server, open Help > JRebel > Configuration and select Startup. Select your desired
Run via IDE – This displays the server launch instructions from within the IDE.
Run locally from command line – Select this option to access JRebel's integrated CLI instructions. You will be presented with a set of drop-down menus. Select your desired Java version and operating system to receive a set of pre-configured instructions. Follow the steps provided to start your external, command line server with JRebel enabled.
Run on a remote server – Select this option to configure JRebel in a JRebel Cloud/Remote setting. Follow the steps provided.
You can also find the CLI instructions within this manual: Running the container from command line.
Disable automatic application deployment¶
Server startup¶
The JRebel plugin for IntelliJ IDEA includes dedicated launch buttons. These buttons are located on the main toolbar and on the navigation toolbar by default. You can also find these commands via the Run menu.
The first button launches the container with JRebel. The second button launches the container with JRebel in debug mode.
By launching the process from one of these buttons, the JRebel plugin will automatically add the appropriate command line parameters.
External servers and remote servers¶
When launching the application server from a command line or using a remote server, open Help > JRebel > Configuration and select Startup. Select your desired
Run via IDE – This displays the server launch instructions from within the IDE.
Run locally from command line – Select this option to access JRebel's integrated CLI instructions. You will be presented with a set of drop-down menus. Select your desired Java version and operating system to receive a set of pre-configured instructions. Follow the steps provided to start your external, command line server with JRebel enabled.
Run on a remote server – Select this option to configure JRebel in a JRebel Cloud/Remote setting. Follow the steps provided.
You can also find the CLI instructions within this manual: Running the container from command line.
Disable automatic application deployment¶
Open the Run/Debug Configuration for the corresponding application server via Run > Edit Configurations. On the Server tab, set On frame deactivation to Do nothing.
Now you can use the Run with JRebel and Debug with JRebel launch buttons to start the selected configuration with JRebel.
JRebel Support¶
You can quickly get in touch with JRebel Support using the embedded support dialog in Help > JRebel > Submit a Support Ticket.
From here, describe your issue and specify your email address for further contact. Enable trace level logging to give JRebel Support more information on what went wrong and choose to add the log files to the support ticket. Press Send when ready.
Updating the IntelliJ IDEA plugin¶
Open Help > Check for Update.
Select JRebel from the list when available.
Press Update to continue.
Complete the installation.
Restart IntelliJ IDEA.
Note
To verify you current JRebel version, open Help > JRebel > Configuration and select the Advanced node. Find your current plugin version. When upgrading from very old plugin versions, a complete plugin uninstall and new version install is recommended instead.
IDE log level configuration¶
You can configure the JRebel IDE plugin log level using a command line parameter. You can add this parameter to your {user.home}/.jrebel/jrebel.properties file.
The default value for this property is info. The JRebel IDE plugin log file itself is stored in {user.home}/.jrebel/.
Also you know ATG builds are not fast, and also ATG applications take some time at start up due start lots of components for first time when starting.
Do the JRebelQuickStart steps
After you are done with it you will end up with something like this:
Jrebel 2019 1 4 Esv
JRebel will reload your .properties files on your ATG installation inside nucleus server, and in order to make that happen, instead of going and changing those on the atg installation you can just point your project to fileSync the files with your atg Installation.
Once these Steps are done, now you can go and change components on the fly without have to Restart, like create new property, no method or inject new component, the only thing that you need to do is make sure you change both your .properties file and your java class, so JRebel redeploys the configuration for the component.
I'll upload a video if these steps in action as soon as I have time.
Enjoy JRebel running on your ATG installation!
Jrebel 2019 1 4 X 4
Very Important Note:Make sure that your project is a java project and also does not have build-path errors, otherwise the auto-compile will not work, so your classes will not be deployed.
Jrebel 2019 1 4 0
If you want to try JRebel, just email at nick.leblanc@zeroturnaround.com to get a trail license for free.
Special Thanks to JRebel team that helped me out on setting my ATG environment to work correctly.
