Thursday, January 20, 2011

JDK1.5 Future for Drools and jBPM

Dropping JDK1.5 is something that rears it's head from time to time, and we know we have to address it sooner or later.

We recognise that the majority of people would like to see JDK1.5 dropped, but there are still a few large critical enterprises using Drools and jBPM on JDK1.5.

Technically for us there isn't a huge advantage, and certainly no "must have" feature, in the same way that moving from 1.4 to 1.5 was. However it does make the project easier to manage: less runtime targets to test against and we don't need to double check people are putting JDK1.6 only classes in Drools and jBPM.

My personally opinion is that we need a widest audience possible for the up coming jBPM5 release and we still have some critical things I'd like to see in Drools first. So personally I'd like to wait until the last few months of this year, say October, before dumping JDK1.5; which would allow for a very late 2011 release or very ealry 2012 release that is JDK1.6+.

What do people think? Comments welcome, I've also added a poll on the right side.

Mark

4 comments:

  1. Note that if you want to use the modeshape connector instead of the jackrabbit connector for Guvnor, you already need to use JDK 6.

    Also, Planner is about 30% faster in JDK 6 compared to JDK 5, last time I checked.

    ReplyDelete
  2. What are the downsides of maintaining 1.5 compatibility?
    Those who wish can always run on anything backwards compatible.

    ReplyDelete
  3. I support Marks opinion, I would stay with Java 5 as long as it gets a real pain, too much enterprise environments still rely on it.

    ReplyDelete
  4. yup, keep the JDK 5 support for now.

    In Java land outdated technologies don't go away quickly; just see how many J2EE 1.4 related questions still fly by in the forums for example, or the staggering amount of people still working with Java 1.4 for some reason or another.

    ReplyDelete