does the problem persist if you close all other projects? Besides, 3.0.12 IS for 3.2, where did you read it is not?
you can also try to disable the older version instead of uninstalling.
Thanks for your response.
I closed all other Eclipse-Projects and tried it again: moved one node on the process definition (via GUI) and saved it -> same problem. CPU usage of 100%.
In the readme.html file of the jbpm-gpd-site-3.0.12.zip, I found that it is only tested with 3.1 version of Eclipse.
Thanks for reporting. I myself noticed short hangups on the cvs branche of the GPD, I never moved from 3.0.11 to 3.0.12.
I think the readme should be updated. afaik, 3.0.12 is only tested against eclipse 3.2. Are there any other plugins installed? If so, is the behaviour the same if you just use a plain eclipse install?
For testing I tried to install the 3.0.12 plugin on a plain, fresh eclipse 3.2 (only JDT included, no WTP or other stuff). The update manager says that the "org.apache.xerces" plugin is required but missing. I'll now search on how to fix this the easiest way - probably installing WTP...
I'll report my results later.
Here I am again.
Now I got really confused. Looking into the jbpm-gpd-site-3.0.12.zip, I saw that the plugins directory already contains the xerces plugin which (as it seems) cannot be found...
...I installed the latest eclipse 3.2.1, the latest WebToolsProject plugin and the designer plugin 3.0.12. Now simply opening the processdefinition.xml takes about 5 minutes and my CPU is getting hot...