On 2025-02-25, Stefan Bodewig wrote: > 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.
It looks as if checkstyle was the only project that depends on guava so it looks as if you really wanted to verify checkstyle isn't broken by guava updates. If you want to see whether a guava update would break checkstyle at runtime (when building Tomcat) then the approach above may work. If all you want is to have the guava dependencies on the classpath when Tomcat is built you could change the project name and the mvn repositoy proxy would not provide the packaged version to checkstyle. Right now I'm not sure why the packaged giava is there. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
