Hi
Guava has been a dependency nightmare and in earlier versions they
broke their APIs from time to time.
I recall seeing a statement from them a year or so ago, where they
acknowledge this and said they would
keep the APIs more stable so users can better use a specific version
of Guava on the classpath despite different frameworks
where set to use another versions.
So hopefully this will get better.
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
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
