Hi, I've used dependency-* plugins from basepom[1], by using basepom, we could consider configuring some of those and use them in Camel. It's a bit laborious to get through all duplicate classes/resources or version conflicts but I think it pays in the end with determinism you get out of it. It *will* be a lot of work...
zoran [1] https://github.com/basepom On Mon, Jun 18, 2018 at 8:55 AM, Dmitry Volodin <dmvo...@gmail.com> wrote: > Hi Camellers! > > The new gRPC version (0.12.0) requires strong own Guava version which is > 20.0, however we have an import with version 19.0 in Camel parent which > cause transient dependency problem in the custom/sample projects importing > camel-grpc component: > > What do you think about potential sulitions: > 1. Add documentation note that users must add following line to custom > pom.xml file > <google-guava-version>${grpc-guava-version}</google-guava-version> for > overriding default guava version. > > 2. Update current google-guava-version in parent from 19.0 to 20.0 which > could relate to the potential problems in other components > > 3. Play with maven enforcer plugin or suggest another solution. > > Thanks in advance. > > -- > Best regards, > Dmitry Volodin -- Zoran Regvart
