Why is Cobertura causing me to have classpath conflicts with ASM?
Cobertura uses ASM to modify your bytecode. There are a few other popular programs that use ASM; Groovy and Hibernate, to name two. You could have problems if Cobertura uses a different version of asm and you add both versions to your classpath. Cobertura only uses ASM when instrumenting. Cobertura does not need ASM in your classpath when running tests. If you’re seeing classpath conflicts, just make sure the asm jar that comes with Cobertura is used only by Cobertura, and only when instrumenting.
Related Questions
- How to resolve conflicts between different ASM API versions available in a global classpath or within the same ClassLoader?
- The pump packings on my ASM airless sprayer are wearing out prematurely. What could be causing the accelerated packing wear?
- Why is Cobertura causing me to have classpath conflicts with ASM?
