> 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.
It may well no longer be a concern with newer releases of ASM. There have been problems in our dev team as different libraries require ASM as a dependency and there were are incompatible API changes between minor releases. > >> 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. That's what we do when necessary. Jar Jar can be found at http://code.google.com/p/jarjar/ Regards Patrick
