Monday, December 10, 2012

JRebel Episode (1): Stop wasting your time!

While talking with Amr Hesham about an implementation for a certain idea as a web application, he mentioned the JRebel. Regardless that he was thinking that it's free (:P) as it's actually under a propitiatory license, I was glad to check about this amazing compiler plugin. As I'm currently suffering the problem that could be fixed using the idea of JRebel. Well, allow me to mention what is JRebel bellow here.

What is JRebel?
JRebel is a JVM-plugin 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. When developers make a change to any class or resource in their IDE, the change is immediately reflected in the deployed application, skipping the build and redeploy phases and preventing an average of 5.25 work weeks per year in redeploys!

Why use JRebel?
JRebel is an alternative solution to updating classes which does not require a debugging session to be started. Instead it monitors the file system for changes and updates the classes in-memory. This means that only classes compiled to ".class" files will be updated and changes to classes in JAR files will be ignored. JRebel imposes a performance overhead on the application and should not be used in production or performance tests. It is meant to be a development tool only.

Support
JRebel is supports a wide range of containers, IDE's and frameworks. For a complete list of all of these you can check here.

Get JRebel
You can download it from here. This is a free trial for 14 days only as it's licensed as proprietary.

To be continued:
JRebel Episode (2): On the spot

References:
http://zeroturnaround.com/software/jrebel/
http://en.wikipedia.org/wiki/JRebel
http://java.dzone.com/articles/reloading-java-classes-401

No comments:

Post a Comment