Twitter github

The Little Things

Some people say it’s the little things that count. I’ve been working on a feature that makes the life of some RCP developers slightly easier. When you export products, you will be given the option to also choose one of your installed JREs to come along with it. This may be news to some people, but if an RCP application has a JRE in the jre directory (under the root directory), the application will automatically use that JRE (see picture below).

It’ll appear in the next I-build once I work out some of the kinks 🙂

  • AlBlue

    Neat idea, but there aren’t many VMs that you can ship with an RCP project. The Sun VMs, for example, require you to redistribute the JRE as a self-installer, rather than an ‘expanded’ VM.

    The OpenJDK may be a non-starter, because the ‘classpath exception’ is legally questionable when the VM is bundled with non-GPL code. Although the intent of the exception is to allow that, it’s not been tested in court.

    Harmony, which has just been promoted to harmony.apache.org, is still a work in progress and as it hasn’t been tested with the TCK it can’t be called Java.

  • AlBlue

    Neat idea, but there aren’t many VMs that you can ship with an RCP project. The Sun VMs, for example, require you to redistribute the JRE as a self-installer, rather than an ‘expanded’ VM. The OpenJDK may be a non-starter, because the ‘classpath exception’ is legally questionable when the VM is bundled with non-GPL code. Although the intent of the exception is to allow that, it’s not been tested in court.Harmony, which has just been promoted to harmony.apache.org, is still a work in progress and as it hasn’t been tested with the TCK it can’t be called Java.