Open stefv opened 2 years ago
If you use Maven then you could use its <dependenciesManagement>
to declare the preferred version of Wicket.
This way the version of the transitive dependency, like pf4j-wicket, will be ignored.
Just make sure all dependencies depend on the same major version of Wicket, i.e. 9
.
I guess there is something similar in Gradle.
Or you can use exclusion
when you declare pf4j-wicket
dependency.
I don't know how many projects/users use this library (I am thinking to not disturb them with an update that contains an updated version of Wicket). @stefv You can propose a PR with an updated version of Wicket, after you test it.
I'm using wicket-spring-boot and pf4j-wicket. The application is refusing to start because it's mixing different versions of Wicket.
To use the last version of Wicket, I'm updating the different projects to Wicket 9.5.0.