Wiki source code of Using JRebel (previously called JavaRebel) with WOLips
Version 35.1 by bogo on 2011/11/07 12:55
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
35.1 | 1 | [[JRebel>>http://jrebel.com]] is a tool from [[ZeroTurnaround>>http://www.zeroturnaround.com]] that makes it possible for Java developers to instantly see any code change made to an app //without// redeploying. JRebel lets you see code changes instantly, versioning classes and resources individually and updating one at a time instead of as a lump application redeploy. |
| |
13.1 | 2 | |
| |
31.1 | 3 | === How to install and use JRebel === |
| |
13.1 | 4 | |
| |
35.1 | 5 | * Get a free 30-day license, a[[open source developer license>>http://sales.zeroturnaround.com]] (Get JRebel for free section) or a paid license from [[ZeroTurnaround>>http://www.zeroturnaround.com]] |
| 6 | * Put the license file (jrebel.lic) into a directory named .jrebel in your home directory. ( /.jrebel/jrebel.lic ) | ||
| 7 | * Get the JRebel plugin. Go to Eclipse->Preferences->Available Software Sites, add [[http://www.zeroturnaround.com/update-site/]] | ||
| |
13.1 | 8 | |
| |
31.1 | 9 | [[image:AddZeroTurnAround.png]] |
| 10 | |||
| 11 | * Download the Jrebel Eclipse Integration and perhaps the JRebel Eclipse Debugger Integration from install new Software | ||
| 12 | |||
| 13 | [[image:InstallSoftware.png]] | ||
| 14 | |||
| 15 | * Make sure you have checked the JRebel Plugin in WOLips if you download the newest version. | ||
| 16 | |||
| 17 | [[image:UpdateWOLipsWithJRebel.png]] | ||
| 18 | |||
| |
35.1 | 19 | * Restart Eclipse. You will now have a Jrebel preference item in your eclipse preferences and JRebel is ready for use with your projects. |
| |
31.1 | 20 | |
| |
13.1 | 21 | You have now installed and setup the stuff that WOLips needs to know about the location of JRebel.jar. |
| 22 | |||
| |
31.1 | 23 | == How do you use it? == |
| |
13.1 | 24 | |
| 25 | Well that has become very simple since the inclusion of Quinton Dolan's JRebel plugin in WOLips. | ||
| 26 | |||
| |
35.1 | 27 | 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 | 28 | |
| 29 | In the Run Configuration of a WOApplication you will notice an extra Tab, called JRebel. | ||
| 30 | |||
| |
35.1 | 31 | Select the tab, and check the check boxes to enable JRebel Agent and (eventually) Enable debug logging. |
| |
13.1 | 32 | |
| |
31.1 | 33 | [[image:EnableJRebel.png]] |
| |
13.1 | 34 | |
| |
35.1 | 35 | Start you project from the Run Configuration. |
| |
13.1 | 36 | |
| |
35.1 | 37 | Suddenly, you will get messages about jrebel being loaded, and some extra information about what settings are available as extra arguments. |
| |
15.1 | 38 | |
| |
35.1 | 39 | {{info}} |
| |
31.1 | 40 | |
| |
35.1 | 41 | 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: |
| 42 | |||
| 43 | \-XX:MaxPermSize=384m | ||
| 44 | |||
| 45 | {{/info}} | ||
| 46 | |||
| 47 | Start changing your java code on the fly: watch and start saving time. | ||
| 48 | |||
| |
31.1 | 49 | [[image:JRebelWOLipsLog.png]] |
| 50 | |||
| |
35.1 | 51 | * Profit (for the europeans: Extra Time Off) |
| 52 | |||
| 53 | == More information == | ||
| 54 | |||
| 55 | [[Old screencast from David Avendasora about using JRebel with Eclipse 3.4>>http://www.wocommunity.org/podcasts/WOJavaRebel_Setup.mov]]. |