What about the fix added in cxf? It tries asm classes then xbean asm then
spring asm. Look asmhelper in cxf. It is a good compromise to avoid
multiple shades.

- Romain
Le 1 mai 2012 11:22, "Mark Struberg" <[email protected]> a écrit :

> Hi!
>
> What do you think of the following idea:
>
> For asm, we could create and maintain own shaded jars which contain the
> major.minor version (not the patch version as I assume they are binary
> compatible) and then other projects can use exactly that version.
>
> That would allow to only have asm on the classpath once if using the same
> version. And other projects could still use a different version.
>
> I will need to try this out and play around. Worst case is that I need to
> add a new functionality to the maven-shade-plugin. But I'm Maven committer
> as well, so nothing which stops me...
>
>
> LieGrue,
> strub
>
>
>
> ----- Original Message -----
> > From: Romain Manni-Bucau <[email protected]>
> > To: [email protected]
> > Cc:
> > Sent: Monday, April 30, 2012 11:15 PM
> > Subject: cxf and asm
> >
> > Hi,
> >
> > if anyone wants to hack on it:
> > https://issues.apache.org/jira/browse/CXF-4246
> >
> > we should now be able to use our asm shaded jar instead of the
> problematic
> > asm one.
> >
> > - Romain
> >
>

Reply via email to