There haven’t been any long posts in a while, and there aren’t going to be any until July probably so get used to it. Writing energies are dedicated elsewhere for a pretty exciting series about—well, you’ll see soon enough.

But as fortune would have it this publication has come into possession of an as-yet undocumented flag for JavaRebel that is just too long to fit in the side column so it has to go into a long post. You see, as an offshoot of version 1.1’s support for “unexploded development” (boom) JavaRebel is now able to process updates to JARs on your classpath, such as libraries all up in your local Maven repository.

For example! If you have a project called “Databinder” that you are always coding simultaneous to dependent apps, which might be in Scala or some other uppity JVM langage that is still too good for Eclipse, now you can mvn install updates to library code just like updates to application classes. Ha! All you have to do is tell JavaRebel which classes to monitor using this new parameter:

-Drebel.packages_include=net.databinder

It applies to the named package and any below it; delimit with commas if you need to set more than one. That is all.