The average Java developer spends around five 40-hour work weeks each year just waiting for app redeploys & app server restarts in order to see changes to their code. That time is simply lost; instead, developers should be spending quality time in their code, not just writing it, but also refactoring and crafting it into the best code they can write.

With that in mind, the beta version of JRebel 6 (coming later in 2014) supports making a whole new class of changes to your code without restarting. Unlike all previous versions, JRebel 6 now supports changes typically made during the refactoring phase of application development. No longer is the power of JRebel limited to only new code!

If you’re impatient, you can jump straight to the group of blog posts, complete with alluring memes and a sense of humor. But here is what we cover, including the instructions for making it happen:

  • Changing Implemented Interfaces without restarting
  • Adding superclasses without restarting
  • Adding new instance fields without restarting

Refactoring existing classes and extracting out common functionality into an interface is a great way to help decouple concrete implementations and generalize methods. The first post of our blog series covers adding and removing implemented interfaces to Java classes:

Next, we look at why extracting the shared functionality and properties of your Java classes into superclasses is an effective way to utilize the strongly typed Object Oriented system in Java and reduce duplication of code in your projects. So, our second post in the series covers adding new superclasses to to Java classes:

The third and final post in the series covers adding new instance fields to Java classes:

If you could imagine spending your coding day without having to restart anything, how great would that be? View all your code changes instantly removes a huge time suck from your day and frees you up to spend more time writing better code faster.

The beta version of JRebel is already bundled into the normal stable release and can be easily activated by clicking a radio button in your IDE plugin or by following these instructions:

Try JRebel 6 beta. Because our bet is that your boss isn’t planning on a future where Java development teams have extra time to wait around for easily-preventable redeploys and restarts that cost the average developer 1 coding hour per day.