Problems moving to groovy 2.1.6

I'm having trouble building in IntelliJ since moving from Groovy 2.1.3 to 2.1.6.   The build works fine as an external Maven build.  It's clearly due to conflicting versions of Groovy (searched enough to figure that out), but I can't find anywhere I'm using anything other than 2.1.6.   Checked so far:

- Made sure POM has right version - in one place only
- Replaced the default groovy-all-2.0.6.jar in IntelliJ IDEA 12.1.2/lib with groovy-all-2.1.6.jar (makes no difference)
- GROOVY_HOME is properly set to my local 2.1.6 install

Not sure where to go from here.   This is what I get when I build the project:

Error:A groovyc error occurred while trying to load one of the classes in project dependencies, please ensure it's present. See the message and the stack trace below for reference
java.lang.IncompatibleClassChangeError: Found interface org.objectweb.asm.ClassVisitor, but class was expected
 at org.codehaus.groovy.classgen.AsmClassGenerator.visitClass(
 at org.codehaus.groovy.control.CompilationUnit$
 at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(
 at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(
 at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(
 at org.codehaus.groovy.control.CompilationUnit.compile(
 at org.jetbrains.groovy.compiler.rt.GroovyCompilerWrapper.compile(
 at org.jetbrains.groovy.compiler.rt.DependentGroovycRunner.runGroovyc(
 at org.jetbrains.groovy.compiler.rt.GroovycRunner.main(
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(
 at java.lang.reflect.Method.invoke(
 at com.intellij.rt.execution.CommandLineWrapper.main(

any thoughts anyone?

1 comment
Comment actions Permalink

Ahh, more searching and I answered it myself.   I had also pulled in org.xerces... which apparently has some conflicting use of ASM.   Using groovy-all instead of groovy fixes it (it has a relocated version of ASM).


Please sign in to leave a comment.