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
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,
Hello, wicket users,
After updating just of wicket version in our projects from 8.0.0 to 8.1.0
we started to see the following exception during rendering time.
Nothing was changed except wicket version. Do you have any suggestions what
hidden dependencies and etc. might lead to this issue?
