3 Replies Latest reply on Aug 26, 2009 5:09 PM by Randall Hauch

    JBoss DNA and JDK 1.6

    Randall Hauch Master

      We're making good progress on the query and search functionality, and hope to have a large portion of the functionality committed to the trunk very soon.

      In the meantime, I'd like to open the discussion of whether we can/should move to requiring JDK 1.6 for JBoss DNA. Please state your thoughts, whether you're a user or a contributor.

      The original ideas were to stick with JDK 1.5 until it was end-of-lifed, hoping to maximize the number of environments in which JBoss DNA could be used. However, J2SE 5.0 (and JDK 5.0) is already in its end of life transition, and is slated for its end-of-life to be completed on October 30, 2009 [1].

      Given our timeframe, I'm not sure its that useful to stay with JDK 1.5. We hope to have 0.6 out well before October 30 (ideally mid-September), with the release being feature-driven by query/search support. The 1.0 release should follow soon after, with TCK compliance being the primary driver. In fact, if we continue to make steady progress on TCK compliance, the 1.0 release could actually be a short release and could very ready even as early the first part of October. All in all, we're pretty close to the JDK 5.0 EOL.

      Of course, we could stay on JDK 1.5 to ensure we support this version of Java, but could also test our releases against JDK 1.6.

      What are your thoughts on either keeping on JDK 5 or switching to JDK 6. If you think its beneficial to stay on JDK 5, when do you think we could/should switch?

      [1] http://java.sun.com/javase/downloads/index_jdk5.jsp