ZeroTurnaround Blog

Product Updates, Company News & Fun

JRebel 3.5 — Open Source Galore

The last few months were very busy here at ZeroTurnaround HQ in the cold and gloomy Estonia. We wanted to deliver something awesome to our users, before we fully switch to working on the larger things planned for the 4.0. To that effect we decided to address some of the long standing requests as well as make some improvements to deliver better on our promise of “All changes reloaded, instantly!”. Whereas the previous major release focused mainly on the Java EE standards, this time we put our attention to supporting various Open Source frameworks and tools.

Last month we ran a survey on development environments (which is still open, btw, feel free to take a couple of minutes and make your voice heard). In the preliminary results we saw that Spring is used in almost half the Java EE apps today, so it’s great to say the 3.5 improves your Spring experience by working better in applications without Spring MVC and with the new plugin for Spring WebFlow that reloads your flow configuration.

The new plugins for OSS frameworks include Tiles, Wicket, Lift and others. We reworked the JRebel core to better support the OSGi containers, like Equinox and Felix. We improved serialization behavior and reflection performance. Scala and Groovy are now officially supported with JRebel. A score of other improvements and fixes is available in the changelog as well. Whew, that’s a lot of things for one release!

Oh, and one more thing — for years one minor, but persistant, annoyance for our users was the extra frames in the stack trace that JRebel introduced. Starting with 3.5 JRebel no longer adds them!

Get it while it’s hot!

  • salient1

    Was never able to get this to work with IntelliJ…I’ll have to try the new version and see if I have any luck.

  • Jevgeni Kabanov

    If you have any problems be sure to post to our forums, now that we have IntelliJ users in our team we can support it much better :)

  • Anton Arhipov

    It shouldn’t make sense if you used IntelliJ or eclipse. JRebel itself is IDE-agnostic. But might it be the JRebel plug-in for IntelliJ that caused hassle?

  • Michal

    Was there any extra work required for Wicket to work? It’s just plain Java.

  • Jevgeni Kabanov

    I think the plugin supported injecting Spring and Seam components into Wicket. Maybe Guice as well, I’m looking into it.