Florian,
at worse, compatibility problems result, depending on the order classes
are loaded in the JVM.
Could you elaborate on how this could create a compatibility issue? As
long as the libraries in the classpath are all based on the same version
of ASM it should be safe, isn't it?
Emmanuel
* Torsten Werner:
On Fri, Oct 28, 2011 at 1:59 PM, Florian Weimer fwei...@bfk.de wrote:
Shipping multiple, different JAR files means that once you load multiple
ASM-using libraries, some of them are bound to use different JARs, and
the JVM will have to open all of them. At best, this wastes
Package: asm3
Version: 3.3.2-1
Shipping multiple, different JAR files means that once you load multiple
ASM-using libraries, some of them are bound to use different JARs, and
the JVM will have to open all of them. At best, this wastes resources,
at worse, compatibility problems result, depending
tags 646921 + wontfix
thanks
On Fri, Oct 28, 2011 at 1:59 PM, Florian Weimer fwei...@bfk.de wrote:
Shipping multiple, different JAR files means that once you load multiple
ASM-using libraries, some of them are bound to use different JARs, and
the JVM will have to open all of them. At best,
4 matches
Mail list logo
