![]() ![]() The file libjrebel64.so is in JRebel's lib directory. XML file will be generated under SRC /resource.Īt this point, package the Spring Boot project as a Jar, upload it to the server, and run the following command to start the project: nohup java -agentpath:/usr/local/jrebel/lib/libjrebel64.so -Drebel.remoting_plugin=true -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9083 -jar xxx.jar Once activated, you need to set the password for the remote connection by executing the following command in JRebel's root directory: java -jar jrebel.jar -set-remote-password 123456789ġ23456789 is the remote password, which is required when IDEA is connected to the server.Īfter the server is successfully configured, the module of remote hot deployment is set in the panel of JRebel in IDEA, as shown below: Remote hot deployment requires the installation and activation of JRebel on the server, as in the previous article: A reverse proxy tool to play around with JRebel. If the selected project or module changes, press CRTL+SHIFT+F9 to automatically recompile and load the changed part without restarting the project. (1) Local startup and DEBUG mode startup, (2) Update button for remote hot deployment. Of course, there is also a startup button in the upper right corner of IDEA, as shown below: Right click on the main Boot class of Spring Boot and the option to Boot with JRebel appears, as shown below: This will generate a rebel.xml file under the project or module's SRC /resource. How to deploy locally?Īfter the JRebel plug-in is installed, enable automatic compilation in IDEA, then go to the tool panel of JRebel in IDEA and check the projects or modules required for hot deployment, as shown below: Local hot deployment only requires a JRebel plug-in in IDEA, and remote hot deployment requires a JRebel plug-in on the server, both of which were covered in the previous article, but you can check it out if you don't: get a reverse proxy tool and play around with JRebel. Modification in a method can implement hot deployment, but the new method or modification of method parameters does not take effect. devtoolsThe hot deployment mode has limited functions.JRebel is not limited to Spring Boot projects, but can be used in any Java project.JRebelLoading speed is better than devtools. ![]() The comparison between the old and the young is not really comparable, and if it weren't for JRebel, it would be the first choice of any programmer. What the hell is this? And such amazing things. Some people hear this and they're dumbstruck. ![]() ![]() Remote hot deployment is the local code changes, do not need to re-package upload server restart project can take effect, local changes can automatically change the project code on the server. In normal development, any changes to the local code must be repackaged and uploaded to the server and then restarted. The term remote hot deployment refers to the remote server. Local hot deployment is the ability to sense changes to specific file code while the project is running and enable the project to take effect without restarting. In traditional development, code changes made during project startup are not recompiled and run, but are only implemented after the project is shut down and restarted. Hereby declare: the author supports the original, not bad money suggested to install an original, after all, such a good tool is worth. The author has written a separate article on how to activate JRebel, which you can check out if you don't have the money: get a reverse proxy tool and play around with JRebel. JRebel beats DevTools in terms of speed of loading and ease of use.Īs an older development tool, JRebel really deserves a chapter. The most popular hot deployment in Spring Boot is DevTools. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |