Yes, this is what I recommend --- use the package renamed version tied to the major ASM version.
But this only works if you are the user of ASM, and not if you need to bundle a library that uses ASM. For this situation, I think Jenkins supports class masking that lets you ignore specific packages from the dependencies and from the core. 2012/7/9 Sandell, Robert <[email protected]>: > Kohsuke write something around this a while back > http://kohsuke.org/2012/03/03/potd-package-renamed-asm/ > > But using those packages might interfere with JaCoCo too much. > > > > > > Robert Sandell > > Software Tools Engineer - Tools and Integration > > Sony Mobile Communications > > > > From: [email protected] [mailto:[email protected]] > On Behalf Of Stephen Connolly > Sent: den 9 juli 2012 10:42 > To: [email protected] > Subject: Re: How to tell Jenkins to use a different ASM version when comes > to a specific plugin? > > > > You can switch the classloader delegation mode (it is a config parameter of > the maven plugin) > > On 8 July 2012 21:48, Ognjen Bubalo <[email protected]> wrote: > > Hello, > > > > In the JaCoCo plugin I would like to use ASM 3.3.1 but the ASM 2.2.3 is > loaded for some reason (maybe Jenkins uses it?). How could I tell Jenkins to > use a newer ASM when the plugin's classes are loaded? > > > > Thank you! > > > > Br, Ogi > > -- Kohsuke Kawaguchi
