![]() ![]() ![]() They describe the configuration in their installation instructions under Step 3.Īfter following these instructions, JRebel should be ready to work with our projects. JRebel recommends to additionally configure the Eclipse debugger in order to ignore synthetic methods. It is already added to our parent project POMs (in the env-development profile), so all you have to do is to update your SVN folders and rebuild the packages that you want to use with JRebel.Īdditional Eclipse debug configuration There is a Maven Plugin available which automatically creates this rebel.xml for our projects. For additional files and directories a config file named "rebel.xml" is required that describes these paths. JRebel has to know which class and resource files it should watch for changes. Add the above line (with your JRebel path) to the VM arguments.Ĭonfiguration of development/build environment.Double click on the server, a settings window will open.noverify -javaagent:c:\programme\javarebel-2.0.3\jrebel.jar Configuration of JBoss in Eclipse Replace the path with your individual complete path to the jrebel.jar file. Add the following line to your JBoss startup VM arguments.In version 2.2.1 you can also choose an installation jar which works quite nicely. Copy the license file (*.lic) to the JRebel directory.Unpack the zip to an arbitrary directory.Luckily, we could convince them of our projects and got free one-year licenses for the OSS-committers at Max Planck Digital Library. JRebel is not free, but supports Open source Projects. This table shows what you can now do without a complete redeployment. It watches for changes in the class and resource files and maps them directly to the application server. JRebel is a great tool that bridges this gap. Unfortunately, Eclipse and other development environments do not support incremental hot deployment in combination with different application servers. This can get very time-consuming and annoying. Whenever you make a change to your Java code or your JSP/ JSF page, you have to rebuild and redeploy the complete application in order to see or debug the changes. 4.1 Additional Eclipse debug configuration.4 Configuration of development/build environment.
0 Comments
Leave a Reply. |