On 18.03.21 01:21, Andrew Gaul wrote [...]> Guava versioning is a perennial source of frustration to users and
maintainers. Unfortunately jclouds (and specifically me) made poor choices by using Guava types in public interfaces. I created some tooling to address this but did not make much progress fixing jclouds itself:https://github.com/gaul/interface-maven-plugin
Thanks for the link. However, at a first glance, this looks more like a tool for warning about undesired class usage. The jenkins parent pom already uses the maven-enforcer-plugin which does something similar (and more) but at pom level (e.g.: in jenkins it blocks transitive dependency on newer guice/java for any plugin)
Would Guava/Guice vendoring work given the existing mess? Could you hack up a partial proof of concept to see if it would work? Vendoring has other caveats so let's what others say.
I am not familiar with the term vendoring. What is that? I only know shading using the maven-shade-plugin. E.g.: This has been used in jclouds in the past (was removed though at a later point in time): https://github.com/apache/jclouds/pull/35 Thanks -Fritz
OpenPGP_0x6E8338980332A6B0.asc
Description: application/pgp-keys
OpenPGP_signature
Description: OpenPGP digital signature
