I have tried with 1.5.0_06 from Sun and now it works.
But I don't see any difference in behaviour by using the version for Eclipse 3.1 or Eclipse 3.2 under Eclipse 3.2, except for the latest one not working under JRockit.

Does the version specific to Eclipse 3.2 address any specific issues?
The Eclipse 3.1 version seems to work ok under Eclipse 3.1.

Not all features work if the plugin for Eclipse 3.1 is installed in Eclipse 3.2. There were changes in the Eclipse platform API from version 3.1 to 3.2 and we had to add some changes in the source code of the plugin. If everything worked for you with the 3.1 plugin installed in Eclipse 3.2 then you did not use those features. You should use only the plugin version for Eclipse 3.2 in Eclipse 3.2.

Use a Java virtual machine from Sun Microsystems as required on the Download page.

BEA Jrockit 1.5.0_06 R26.4.0 works with Eclipse 3.2 and the OxygenXML 7.2 plugin for Eclipse.

Instead of just saying use a SUN Java Virtual machine, it would be more helpful to indicate which maintenance release of the virtual machine should be used, as it appears that some features are being used or added to the SUN virtual machine, that may not have made it into other virtual machines release updates.

There are many valid reasons for using another virtual machine, and garbage collection is a big one which Jrockit excells.

We will make the note about the supported JVMs more explicit on the Download page and in the User Manual: <oXygen/> supports JVMs 1.4.2 or later from Sun Microsystems and from Apple Computer (on Mac OS X). It is not a problem of features added or deleted from the Sun JVM as <oXygen/> does not require non-standard features of the JVM or Java classes other than the standard core ones distributed with the JVM. <oXygen/> may work very well with JVMs from other vendors but we had the experience of JVMs from other vendors than Sun Microsystems and Apple Computer which are not conformant to the JVM specification. For example the JVM called "GNU libgcj" from Free Software Foundation distributed as the default JVM on Ubuntu Linux does not include a standard encryption provider which is required for implementations of the JVM specification and which is used in <oXygen/> to verify the license key pasted by the user at the first startup. That means any <oXygen/> license key is rejected when the user pastes it in <oXygen/>. This and other JVM implementation problems are very annoying for users who do not have the time to test several virtual machines from different vendors before they can even register their license key and start to use a pure Java application (no native code) normally.

So feel free to try and use JVM implementations from other vendors like BEA Systems but we do not provide user support for <oXygen/> malfunctions caused by bugs in the JVM implementation.

What might be helpful then to the use community is that, as you get a list of JVMs from the user community that have been tested to work, just provide that list as a knowledge base item or FAQ. With the stipulation that the only supported JVM that you test yourself are the SUN JVMs.

We will specify on the Download page the JVMs that do not work with oXygen, like GNU libgcj and also we will specify the JVMs which we support (Sun Microsystems and Apple Computer). A JVM will have to be tested extensively with oXygen in order to be added to the list of supported ones. oXygen may work well with other virtual machines like JRockit but we will not support users reporting problems caused by bugs in these JVM implementations.

On the Download page in the section Requirements we list the supported JVM implementations and the implementations that do not work with oXygen due to the bugs that they contain. Currently only the JVM implementation from Sun Microsystems is supported.