Peter Firmstone wrote: > using a custom namespace for the ASM library, Patrick pointed out on an > earlier discussion that ASM's API is subject to change, I suspect that > this will settle down as the library matures, however in the mean time,
This concern is really old and outdated. The current stable release - both in terms of runtime stability and change rate - is 3.1 and was released almost two years ago. > we don't want it stepping on user code using different versions of ASM > within the same namespace. This process can be automated easily with e.g. jarjar. -h
