![jrebel liferay remote server jrebel liferay remote server](https://www.imab.dk/wp-content/uploads/2018/12/2018-12-30-08_00_14-Firmaportal.png)
Visit the Developer Corner to learn how to obtain and use the plugin, and how to build it and contribute to this project. Therefore, this project seems to add hook/theme frameworks and resolve some other issues. It works for most of the use cases with Liferay, but not all. The reason why this project exists is that JRebel does not 100% work with Liferay's class loading and other JVM-level behaviors. This style of basic integration is no problem. You can use JRebel right now for standard portlet development. This is very useful for Liferay Developers, who spend a lot of time waiting on their systems to compile, deploy, and re-initialize many components during a development session. When you change any class or resource in your IDE, the change is immediately reflected in the application, skipping the build and redeploy phases. They were on the same machine, but the setup and configuration is essentially the same. I have worked with a similar setup: Tomcat server + Remote debugging in Eclipse for enhanced class redefinition. JRebel maps your project workspace directly to the application under development. You can use DCEVM+HotSwapAgent in the virtual machine and connect to it via your remote debugger in IDE in host machine. Full support of instance changes made in plugin descriptors (portlet.xml,liferay-hook.xml.).Full support of Liferay hook framework (allow any changes in any type of hook to be automatically reflected in the portal).Full support of Liferay theme framework (allow the user to edit all static files in the IDE).
![jrebel liferay remote server jrebel liferay remote server](https://cabrerahector.com/wp-content/uploads/2020/05/bitbucket-pipelines-ftp-deployment-demo.gif)
This project is aimed to develop a plugin for JRebel with the following goals: What is the JRebel/Liferay Integration Project?