I would add a specific guava-version property only for gRPC and gRPC Karaf
feature.
This is what we usually do for Guava stuff.
--
Andrea Cosentino
----------------------------------
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Monday, June 18, 2018, 8:55:37 AM GMT+2, 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
