Wiki source code of Using JRebel (previously called JavaRebel) with WOLips
Version 31.1 by Kieran Kelleher on 2010/09/07 19:39
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
25.1 | 1 | JRebel (previously called javarebel is a tool from [[ZeroTurnaround>>http://www.zeroturnaround.com]]). |
| |
13.1 | 2 | |
| |
31.1 | 3 | It is a java library that makes it possible to change java code while running a project in WOLips and see the results without having to restart. It is a great timesaver. |
| |
17.1 | 4 | |
| |
25.1 | 5 | If you are running Eclipse 3.4, you should have a look at the screencast from David Avendasora at [[http://www.wocommunity.org/podcasts/WOJavaRebel_Setup.mov]]. |
| 6 | |||
| |
31.1 | 7 | If you are running WOLips 3.5.1 or bigger, you are lucky: the JRebel plugin is included in the current WOLips for there versions. |
| |
25.1 | 8 | |
| |
31.1 | 9 | === How to install and use JRebel === |
| |
13.1 | 10 | |
| |
31.1 | 11 | * Download you version from [[ZeroTurnaround>>http://www.zeroturnaround.com]] |
| 12 | * put the jrebel.jar somewhere nice, so you can use it in whatever project you are working | ||
| 13 | * Go to WOLips->Preferences->Install Software, add [[http://www.zeroturnaround.com/update-site/]] | ||
| |
13.1 | 14 | |
| |
31.1 | 15 | [[image:AddZeroTurnAround.png]] |
| 16 | |||
| 17 | * Download the Jrebel Eclipse Integration and perhaps the JRebel Eclipse Debugger Integration from install new Software | ||
| 18 | |||
| 19 | [[image:InstallSoftware.png]] | ||
| 20 | |||
| 21 | * Make sure you have checked the JRebel Plugin in WOLips if you download the newest version. | ||
| 22 | |||
| 23 | [[image:UpdateWOLipsWithJRebel.png]] | ||
| 24 | |||
| 25 | * Restart Eclipse. You will now have a Jrebel preference item in your eclipse preferences | ||
| 26 | * Goto to Preferences->JRebel, and point the Path to jrebel.jar to the jrebel.jar location from action 2. | ||
| 27 | |||
| 28 | [[image:PathToJRebel.png]] | ||
| 29 | |||
| |
13.1 | 30 | You have now installed and setup the stuff that WOLips needs to know about the location of JRebel.jar. |
| 31 | |||
| |
31.1 | 32 | == How do you use it? == |
| |
13.1 | 33 | |
| 34 | Well that has become very simple since the inclusion of Quinton Dolan's JRebel plugin in WOLips. | ||
| 35 | |||
| |
31.1 | 36 | For a project in which want to use jrebel to change java code while running, go to the run configuration of the project, under the contextual menu Run As->Run Configurations. |
| |
13.1 | 37 | |
| 38 | In the Run Configuration of a WOApplication you will notice an extra Tab, called JRebel. | ||
| 39 | |||
| |
31.1 | 40 | Select the tab, and check the check boxes to enable JRebel Agent and (eventually) Enable debug logging. |
| |
13.1 | 41 | |
| |
31.1 | 42 | [[image:EnableJRebel.png]] |
| |
13.1 | 43 | |
| |
31.1 | 44 | Start you project from the Run Configuration. |
| |
13.1 | 45 | |
| |
31.1 | 46 | Suddenly, you will get messages about jrebel being loaded, and some extra information about what settings are available as extra arguments. |
| |
15.1 | 47 | |
| |
31.1 | 48 | {{info}} |
| 49 | |||
| 50 | If you get out of memory error with respect to "Perm Gen space", just allocate more Perm Gen memory in command line launch args in your launch configuration. For example: | ||
| 51 | |||
| 52 | -XX:MaxPermSize=384m | ||
| 53 | |||
| 54 | |||
| 55 | {{/info}} | ||
| 56 | |||
| 57 | Start changing your java code on the fly: watch and start saving time. | ||
| 58 | |||
| 59 | [[image:JRebelWOLipsLog.png]] | ||
| 60 | |||
| 61 | * Profit (for the europeans: Extra Time Off) |