Use mvn dependency:tree to capture your actual classpath before and after
the upgrade; this should help you identify where the clash is in your
classpath. You can then use exclusions or dependencyManagement to pick up
the correct version. I use IntelliJ and the "Maven Helper" plugin is
invaluable
Hi,
I guess it is the upgrade of CGLIB and ASM:
https://issues.apache.org/jira/browse/WICKET-6552
Please check whether you have more than one version of ASM in your
classpath. Maybe another dependency in your app depends on ASM 5.x
On Thu, Nov 1, 2018 at 9:35 AM Илья Нарыжный wrote:
> Hello, wi
