Have you ever seen an exception like this:
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'XY' defined in class path resource [applicationContext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans. BeanInstantiationException: Could not instantiate bean class [XY]: Constructor threw exception; nested exception is java.lang.LinkageError: You are trying to run JAXB 2.0 runtime (from jar:file:/.../WEB-INF/lib/jaxb-impl-2.1.8.jar!/com/sun/ xml/bind/v2/model/impl/ModelBuilder.class)but you have old JAXB 1.0 runtime earlier in the classpath (at jar:file: /.../WEB-INF/lib/jaxb-impl-1.0.4.jar!/com/sun/xml/bind/ WhiteSpaceProcessor.class) Please remove the JAXB 1.0 runtime for 2.0 runtime to work correctly.
Well, I have, several times… and the task of having to figure out which library causes this dependency conflict seemed unresolvable pretty scary at first! Luckily, there is the m2eclipse plug-in with its excellent dependency graph. So if you are using Eclipse, whether you are actually using m2eclipse to manage your project or not, just the dependency graph makes it worth having a look at it. I still run my maven tasks on the command line, but have m2eclipse installed, just to be able to use the graph.
After identifying which library is causing the dependency conflict, all you have to do is to add an “exclude” node to that dependency in your pom.xml. In the above case, this snipped did the trick:
<dependency> <groupId>...</groupId> <artifactId>...</artifactId> <version>...</version> <exclusions> <exclusion> <artifactId>jaxb-impl</artifactId> <groupId>javax.xml</groupId> </exclusion> ... </exclusions> </dependency>