> On 30. Aug 2023, at 17:20, Maxim Solodovnik <solomax...@gmail.com> wrote: > > So we have conflict :( > > Maybe it worth to add some redundancy to our dependency:tree and add > `wicket-util` as direct dependency of `wicket-core`?
You can use the maven-dependency-plugin to scan Java classes in a module for uses of classes from dependencies. It is a good practice to have explicit dependencies in the POM for any classes that are used in the current module instead of relying on transitive dependencies to provision a compatible version. https://maven.apache.org/plugins/maven-dependency-plugin/analyze-mojo.html Using the maven-dependency-plugin "analyze" mojo and sticking to its recommendations usually helps avoiding this type of problem. Note that the analysis is not perfect (it uses the class files, not the source files as input, so some things it cannot detect which may lead to wrong recommendations) - but it is quite a useful approximation. Cheers, -- Richard
