Groovy-Eclipse sometimes drops spurious errors in the editor saying that a constructor added by @TupleConstructor can't be found, but these are generally cosmetic and don't result in actual compilation errors (i.e., no markers, code runs).

However, I've discovered that as of 3.0.7 having a static nested class (a record for a command type) annotated with @TupleConstructor causes actual errors using the Groovy-Eclipse compiler; the previous false alarm does generate a marker and a failing class file. A full clean and build, which usually handles mismatches because everything's available, doesn't help. mvn compile with groovyc works fine.