Tom Schindl schrieb: > I can feel your pain. Thank god I'm using OSGi and can declare my > dependencies explicitly :-) Yep. Well, it works for those libs that are just internal implementation details. I'm not an OSGi expert, but if any exported class contains a public or protected method that has type T as a parameter or return type, then aren't you again locked into a single application-wide version of the lib that provides T? If so, then OSGi will solve problems for things like ASM which are usually pure internal details, but will not solve problems for things like commons libs whose types are commonly part of another lib's exported API (lang.enums.Enum, lang.math.DoubleRange, etc)... Regards, Simon --------------------------------------------------------------------- To unsubscribe, e-mail: For additional commands, e-mail: