Compared with pom.xml, it needs to be sent directly to the server. I found that it must have not found the springboot resource file from the jar package. When I continue to execute the mvn command, I found that some packages have been missing after downloading various dependent packages, combined with errors and Since I want to put it under pom.xml, I simply put pom.xml on the server for a try. I was obviously at a loss, so I found a solution for a long time and the problem has not been solved. This statement is very strange!! I typed a jar package on the server, and you asked me to operate in the directory where pom.xml is located. zt-zip before 1.13 is vulnerable to directory traversal, allowing attackers to write to. To run mvn spring-boot:run -Drun.jvmArguments="-agentpath:/lib/libjrebel64.so -Drebel.remoting_plugin=true", be sure to put it in the pom directory None, Remote, Medium, Not required, None, Partial, Partial. (The summary here is more comprehensive) Search: Jetbrains License Server Configuration. There are several solutions to check online information I can’t find the plug-in prefixed with spring-boot. Maybe it is not deployed, or project's ID in rebel-remote.xml is different on the server. Warning: Cannot find a project with ID'' on this remote server. So far, it is reasonable to say that the upload is successful, that is, the synchronization is successful, but there are still many bugsĢ. This file is used to distinguish between the different application. Update directly Click to update the jar package on the remote serverĤ. JRebel remote server support requires the rebel-remote.xml configuration file to operate. Mvn spring-boot:run -Drun.jvmArguments="-agentpath:/lib/libjrebel64.so -Drebel.remoting_plugin=true" Send the jar package to the server and execute java "-agentpath:/lib/libjrebel64.so" -Drebel.remoting_plugin=true -jar on the server settings->plugins->download jrebel plugin->The download is complete and restart the idea Finally, I will talk about the solutions. JRebel is a commercial developer productivity tool for automatic, real-time update of Java code in the running application. There are a lot of pits and various bugs in this project. #tomcat.javaoptions=-agentpath:/jrebel/lib/libjrebel64.so -Drebel.Let me talk about the normal steps first. Or you can download Jrebel manually and then in local.properties add the path: bugjavaoptions=-Xverify:none -agentpath:/jrebel/lib/libjrebel64.so -Drebel.remoting_plugin=true -Drebel.remoting_port=12345 -Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=8000,suspend=n #tomcat.javaoptions=-agentpath:/opt/jrebel/lib/libjrebel64.so -Drebel.remoting_plugin=true In local property change depending on debugging: local.properties( -agentpath depends on where you downloaded your Jrebel): bugjavaoptions=-Xverify:none -agentpath:/opt/jrebel/lib/libjrebel64.so -Drebel.remoting_plugin=true -Drebel.remoting_port=12345 -Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=8000,suspend=n You can add JRebel in your Dockerfile: RUN wget -O jrebel.zip
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |