UPDATE, Apr 19 2009: This does not fix all compiler crashes in Eclipse. This is only useful for the compiler crashes where an Eclipse JVM configuration is used. Please see my later blog post for a better fix and disregard this information.
This is the same error I hit before (see my earlier post), but it happens in Eclipse during the “deploy to AppEngine” phase. You’ll see it if you’ve got a project configured with a 1.6 JVM on the build path (even if your .class compatibility is set to 1.5). It’s not obvious how to fix this at first glance - I had to dig around to find the options that Eclipse passes to the JVM.
You can fix it by adding the same compiler workarounds we explored before to your JVM default arguments. IMPORTANT NOTE: Add the args to all of your 1.6 level installed JVMs. I’ve found that Eclipse doesn’t always choose the selected one if there’s an equivalent also installed (ie: it may use your ‘1.6’ JVM if you have ‘1.6.0’ selected).
-XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/DataTreeNode,forwardDeltaWith -XX:CompileCommand=exclude,org/eclipse/jdt/internal/compiler/lookup/ParameterizedTypeBinding,<init> -XX:CompileCommand=exclude,org/eclipse/jdt/internal/compiler/lookup/ParameterizedMethodBinding,<init>
Add them to your JVMs under Preferences > Java > Installed JREs by clicking the edit button and filling out “Default VM Arguments”:Read full post