US and Worldwide: +1 (866) 660-7555
Results 1 to 3 of 3

Thread: [Mondrian] JDK 1.7

  1. #1
    Julian Hyde Guest

    Default [Mondrian] JDK 1.7

    JDK 1.7 is out (see http://www.oracle.com/technetwork/ja...ads/index.html), and mondrian and olap4j won't currently build.

    The main problem is as for JDK 1.6, when they introduced JDBC 4.0. JDBC 4.1, introduced in JDK 1.7, has a few new methods in important interfaces, so classes that claim to implement those interfaces need to either be declared "abstract", or implement the methods (which sometimes causes other problems). It's not quite as serious, because this time the new methods don't depend on new classes.

    I'm currently fixing mondrian and olap4j so that they build under JDK 1.7. (They probably already run under JDK 1.7. I haven't tried.)

    Julian
    _______________________________________________
    Mondrian mailing list
    Mondrian (AT) pentaho (DOT) org
    http://lists.pentaho.org/mailman/listinfo/mondrian

  2. #2
    Julian Hyde Guest

    Default Re: [Mondrian] JDK 1.7

    I fixed this. As of perforce change 14733, mondrian can builds on JDK 1.7; and as of svn change 479, olap4j can build on JDK 1.7.

    Mondrian and olap4j can still build on JDK 1.5 and 1.6. As long as you are not building a release, you can build under your favorite JDK: 1.5, 1.6 or 1.7.

    If you are building a release, you must use JDK 1.5, and you must have JDK 1.6 and 1.7 installed also. You will notice that mondrian and olap4j both have a new script buildOnJdk.sh (or buildOnJdk.bat for windows users). When building a release, the ant script calls out to this to build selected java files under JDK 1.6 and 1.7. This allows us to ship drivers that implement JDBC 3.0 (JDK 1.5), JDBC 4.0 (JDK 1.6) and JDBC 4.1 (JDK 1.7). All of the drivers are in the same jar. The driver will automatically select the right implementation at runtime.

    Julian

    On Nov 2, 2011, at 9:49 AM, Julian Hyde wrote:

    > JDK 1.7 is out (see http://www.oracle.com/technetwork/ja...ads/index.html), and mondrian and olap4j won't currently build.
    >
    > The main problem is as for JDK 1.6, when they introduced JDBC 4.0. JDBC 4.1, introduced in JDK 1.7, has a few new methods in important interfaces, so classes that claim to implement those interfaces need to either be declared "abstract", or implement the methods (which sometimes causes other problems). It's not quite as serious, because this time the new methods don't depend on new classes.
    >
    > I'm currently fixing mondrian and olap4j so that they build under JDK 1.7. (They probably already run under JDK 1.7. I haven't tried.)
    >
    > Julian



    _______________________________________________
    Mondrian mailing list
    Mondrian (AT) pentaho (DOT) org
    http://lists.pentaho.org/mailman/listinfo/mondrian

  3. #3
    Julian Hyde Guest

    Default Re: [Mondrian] JDK 1.7

    On Nov 7, 2011, at 10:43 AM, Julian Hyde wrote:

    > I fixed this. As of perforce change 14733, mondrian can builds on JDK 1.7; and as of svn change 479, olap4j can build on JDK 1.7.


    One more thing. There are indications that JDK 1.7 is quite a bit faster than JDK 1.6. It isn't exactly a benchmark, but here were the running times I measured for the Mondrian suite, running against MySQL on 64 bit ubuntu 11.10:

    JDK 1.5.0_22 537s
    JDK 1.6.0_24 420s
    JDK 1.7.0_01 365s

    You may be able to achieve similar improvements by upgrading to a recent JDK 1.6 (e.g. JDK 1.6.0_29), but still, it's good to have a reason to stay current.

    It's nice that the JDK isn't like Windows or iOS, where every release seems to get slower.

    Julian

    _______________________________________________
    Mondrian mailing list
    Mondrian (AT) pentaho (DOT) org
    http://lists.pentaho.org/mailman/listinfo/mondrian

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •