Dependency problem with Spring 3.2 with Spring Data JPA 1.2

[dmorley]

On my project on which I was successfully using Spring Data JPA 1.2.0.RELEASE with Spring 3.1, I just changed my Maven dependency for spring-core to 3.2.0.RELEASE. I am getting a java.lang.IncompatibleClassChangeError when attempting to start my web container. Here's a sample of the stacktrace:

Caused by: java.lang.IncompatibleClassChangeError: class org.springframework.core.type.classreading.ClassMetadataReadingVisitor has interface org.springframework.asm.ClassVisitor as super class
	at java.lang.ClassLoader.defineClass1(Native Method) ~[na:1.6.0_29]
	at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) ~[na:1.6.0_29]
	at java.lang.ClassLoader.defineClass(ClassLoader.java:615) ~[na:1.6.0_29]
	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) ~[na:1.6.0_29]
	at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1814) ~[tmp8994960648441534081jbossweb.jar:4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)]
	at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:872) ~[tmp8994960648441534081jbossweb.jar:4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)]
	at org.jboss.web.tomcat.service.WebAppClassLoader.findClass(WebAppClassLoader.java:75) ~[tmp6658054736622098672jbossweb-service.jar:4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)]
	at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1325) ~[tmp8994960648441534081jbossweb.jar:4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)]
	at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1204) ~[tmp8994960648441534081jbossweb.jar:4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)]
	at java.lang.ClassLoader.defineClass1(Native Method) ~[na:1.6.0_29]
	at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) ~[na:1.6.0_29]
	at java.lang.ClassLoader.defineClass(ClassLoader.java:615) ~[na:1.6.0_29]
	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) ~[na:1.6.0_29]
	at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1814) ~[tmp8994960648441534081jbossweb.jar:4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)]
	at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:872) ~[tmp8994960648441534081jbossweb.jar:4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)]
	at org.jboss.web.tomcat.service.WebAppClassLoader.findClass(WebAppClassLoader.java:75) ~[tmp6658054736622098672jbossweb-service.jar:4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)]
	at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1325) ~[tmp8994960648441534081jbossweb.jar:4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)]
	at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1204) ~[tmp8994960648441534081jbossweb.jar:4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)]
	at org.springframework.core.type.classreading.SimpleMetadataReader.<init>(SimpleMetadataReader.java:58) ~[spring-core-3.2.0.RELEASE.jar:3.2.0.RELEASE]
	at org.springframework.core.type.classreading.SimpleMetadataReaderFactory.getMetadataReader(SimpleMetadataReaderFactory.java:80) ~[spring-core-3.2.0.RELEASE.jar:3.2.0.RELEASE]
	at org.springframework.core.type.classreading.CachingMetadataReaderFactory.getMetadataReader(CachingMetadataReaderFactory.java:101) ~[spring-core-3.2.0.RELEASE.jar:3.2.0.RELEASE]
	at org.springframework.context.annotation.ClassPathScanningCandidateComponentProvider.findCandidateComponents(ClassPathScanningCandidateComponentProvider.java:237) ~[spring-context-3.1.2.RELEASE.jar:3.1.2.RELEASE]
	... 150 common frames omitted

My suspicion is that the culprit is Spring Data JPA 1.2.0's dependency on spring-asm, based on my reading of section C.3 of the appendices with the release notes.

Am I correct in my suspicion? Is there any way (beyond waiting for an update to spring-data-jpa) around this?

Thanks in advance!

[NicoTexas]

Same here.
Hope the Spring Data JPA will be upgraded quickly as I would love to use the new Test features in Spring 3.2.
Any time frame for an update ?

[andrewcelerity]

Just hit this too. You might be able to work around it with an exclusion:

<dependency>
	<groupId>org.springframework.data</groupId>
	<artifactId>spring-data-jpa</artifactId>
	<version>${spring-data-jpa.version}</version>
	<exclusions>
		<exclusion>
			<groupId>org.springframework</groupId>
			<artifactId>spring-aop</artifactId>
		</exclusion>
	</exclusions>
</dependency>

[jack.white]

That didn't work for me. Are there any other ideas how to workaround this issue?

[ilyaskorik]

Similar problems. Something has changed for the better?

P.S. Spring Data developers are reading this forum? You have a mess on the site! The latest version 1.1.0, when there is 1.2 and we are all waiting for 1.3. Also, links are not working, try to open the link to CI Build. Pay attention.

[Oliver Gierke]

Spring Data JPA works fine with Spring 3.2. We have several sample applications running this combination. See [0] for example. Please make sure you correctly set up your dependencies overriding *all* of the Spring Data JPA dependencies and locally define the versions of the Spring Framework library version to 3.2.0.RELEASE.

Use mvn dependency:list to make sure you have succeeded in unifying all versions to 3.2.0.RELEASE. In some cases it might be enough to define the Spring Data JPA dependency *after* the Spring libraries as Maven will then favor the dependency version of the transitive dependencies of the Spring libraries instead of Spring Data JPA (i.e. will pull transitive libraries in 3.2, instead of 3.1.3).

@ilyaskorik - what's the reason for this agressive tone? What's so hard about doing a Maven Central search [1] for the latest version? What's so hard about knowing how Maven dependency management works? You know, I hate writing replies like these but you're not serving anyone with this harsh tone. We're definitely open for feedback of any kind but there's no reason to offend people like this.

[0] https://github.com/olivergierke/spring-restbucks
[1] http://search.maven.org/#search%7Cga...pring-data-jpa

[ilyaskorik]

After several experiments with a fresh mind, the following entry in maven pom has helped me:

<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-aop</artifactId>
<version>${version.spring}</version>
</dependency>

[NicoTexas]

After several experiments with a fresh mind, the following entry in maven pom has helped me:

It didn't help me by itself. However, I had a look at my dependency hierarchy and figure out I was getting Spring-asm 3.1.1 from Spring-faces 2.3.1 which have a dependency to Spring-mvc 3.1.1...
So adding

		<dependency>
			<groupId>org.springframework</groupId>
			<artifactId>spring-webmvc</artifactId>
			<version>${spring.version}</version>
		</dependency>

resolved it for me.
Bottom line, you want to get rid of spring-asm.