Installing Plug-ins under ECLIPSE Juno and Java 1.7

Well, we hoped this one would go away, but even with the latest (JDK 1.7.0_51 as of today), the problem we saw with Indigo and Java 1.7 still exists. This problem results from the way Oracle modified Array.sort() in a threading environment. Unfortunately, as of the day I posted this, the NSDEE 4.0 installation instructions did not include a discussion of how to deal with this problem. You will find a discussion of what the ECLIPSE contributors have done relating to this problem here:

The problem was further diagnosed as being: with regards to Mirror Ranking.

So far, we have found two temporary solutions:

  1. For ECLIPSE 3.6.x to 4.2.2 modify the config.ini file found in the ECLIPSE configuration directory (eclipse/configuration/config.ini) and add the following parameter:
  2. Run ECLIPSE 3.6.x to 4.2.2 using the Java 6 JRE/JDK.
    Revisions 6_20 upward are acceptable to ECLIPSE. You can still build
    with the Java 7 JDK by configuring your compilers internally to
    ECLIPSE through Window/Preference.

This is of particular importance to NSDEE 2.x, NSDEE 3.x, and NSDEE 4.x users that have a large number of dependencies to ECLIPSE CDT components installed in a combination of remote update sites and local archives.

The problem has been either not been resolved for ECLIPSE 3.7.1 and above or was reintroduced. See the Indigo post for the original support note.

3 thoughts on “Installing Plug-ins under ECLIPSE Juno and Java 1.7”

  1. The support case has been updated with information relating to ECLIPSE Juno and Java 1.7.

  2. I have tried Option 1 on Windows 8, Juno, Java 1.7 using the java version of ECLIPSE supplied with the NSDEE-4.0 distribution and was successful! Happy developing.

Comments are closed.