thanks for the quick response, which fixed my problem!
Yes, we use Maven and I found that the dependency com.sun.jersey:jersey-server:1.16 has a dependendy to asm 3.1. I tried to exclude that dependendy from jersey-server and use rest-assured without exclusions but then the IncompatibleClassChangeError appeared again. So I'm not exactly sure what caused the problem in my case.
However, it works now. Thx
Am Freitag, 12. April 2013 08:36:07 UTC+2 schrieb Johan Haleby:
Thanks for your comments. Are you using Maven? In that case you may have conflicting versions of asm in classpath. REST Assured depends on Groovy 2.1.2 which depends on asm 4.x which is not backward compatible with asm 3.x. I actually had the same issue myself in my current project where Groovy and jersey-spring were in conflict. In that case you can do something like this:
<!-- There's a classpath clash with groovy and jersey-spring in because of incompatible asm versions, let's
depend on groovy-all instead which fixes the problem. -->
<!-- Needs to be the same version that REST Assured depends on -->
Please see if it works for you. I'll probably add this to an FAQ and write a blog about it if it works.