sorry, I really didn't find time to lend a hand, and I'm not sure I really am much of a help, either.
The class that the plugin doesn't find is com.google.common.util.concurrent.internal.InternalFutureFailureAccess which is required by guava This is when I run dependency:tree [INFO] +- com.google.guava:guava:jar:33.4.0-jre:compile [INFO] | +- com.google.guava:failureaccess:jar:1.0.2:compile [INFO] | +- com.google.guava:listenablefuture:jar:9999.0-empty-to-avoid-conflict-with-guava:compile com.google.guava:failureaccess:jar provides the class. When I look at the error I see the plugin has a classpath that does not contain failureaccess but it contains guava-16.0.1.jar . We provide guava as a packaged dependency https://vmgump.apache.org/google-guava/google-guava/gump_file/list_google-guava_dir1_google-guava.html and I believe the plugin gets guava 33 instead of guava 16 that it expects - because this is what the proxy returned when Maven tried to downkad guava 16. >From looking through the guava issues the dependency on failureaccess has been added around version 23. So the plugin doesn't depend on the failureaccess jar (16 didn't need it) but will need it when using guava 33. The json-schema-validator has not been touched for more than eight years, so it is unlikely to have new releases that depend on newer versions of guava, ever. At first glance there doesn't seem to be any property to disable the plugin and I don't believe you can "install" without running "verify". One option may be to build checkstyle before providing "guava" with separateLocalRepository set to true. This is assuming you want to build any other project that depend on guava and see whether it breaks and you don't care if guava updates not currently dependend on break checkstyle. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
