Repackage asm 4.0 with jarjar to allow different versions of asm coexist

[ghost]

From Daniel.Y...@gmail.com on November 27, 2012 05:15:45

ASM guys suggest repackaging your asm jar files with jarjar if you want to use different versions of asm in your project. In fact, spring team repackaged asm into their own package name to avoid potential conflict.
In my project, I have two repackaged versions of asm and a standard one which is 3.1. If I use the latest reflectasm I have to put asm 4.0 into my class path which will conflict.

Original issue: http://code.google.com/p/reflectasm/issues/detail?id=12

[ghost]

From nathan.s...@gmail.com on November 26, 2012 20:39:49

This seems to come up a lot for Kryo, which uses ReflectASM. If everyone would just use the latest ASM there wouldn't be an issue. The solution is to use something like Maven which has a plugin that can create a "shaded" JAR. I don't want to repackage the ASM in ReflectASM because if someone is using ReflectASM and ASM 4 then they would have two of the same ASM versions unnecessarily.

Status: WontFix