You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Dmitry Volodin <dm...@gmail.com> on 2018/06/18 06:55:31 UTC
gRPC and Google Guava version
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
Re: gRPC and Google Guava version
Posted by Pascal Schumacher <pa...@gmx.net>.
Am 18.06.2018 um 10:36 schrieb Claus Ibsen:
> 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.
Yes, I think they wait longer before deleting deprecated stuff nowadays,
but they still break binary compatibility by deleting methods etc., e.g.:
https://github.com/google/guava/commit/ce6d93c20e143db79cc6b5c42109ca702e3acd55
Re: gRPC and Google Guava version
Posted by Claus Ibsen <cl...@gmail.com>.
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 <dm...@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
Re: gRPC and Google Guava version
Posted by Zoran Regvart <zo...@regvart.com>.
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 <dm...@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
Re: gRPC and Google Guava version
Posted by Andrea Cosentino <an...@yahoo.com.INVALID>.
The I probably would go with the solution at point 1 for the moment.
--Andrea Cosentino ----------------------------------Apache Camel PMC ChairApache Karaf CommitterApache Servicemix PMC MemberEmail: ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd
On Monday, June 18, 2018, 10:53:40 AM GMT+2, Dmitry Volodin <dm...@gmail.com> wrote:
Andrea,
I added this, but spring boot example doesn't work without explicit version
(20.0) defined.
--
Best regards,
Dmitry Volodin
2018-06-18 11:41 GMT+03:00 Andrea Cosentino <an...@yahoo.com.invalid>:
> 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: ancosen1985@yahoo.com
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Monday, June 18, 2018, 8:55:37 AM GMT+2, Dmitry Volodin <
> dmvolod@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
>
Re: gRPC and Google Guava version
Posted by Dmitry Volodin <dm...@gmail.com>.
Andrea,
I added this, but spring boot example doesn't work without explicit version
(20.0) defined.
--
Best regards,
Dmitry Volodin
2018-06-18 11:41 GMT+03:00 Andrea Cosentino <an...@yahoo.com.invalid>:
> 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: ancosen1985@yahoo.com
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Monday, June 18, 2018, 8:55:37 AM GMT+2, Dmitry Volodin <
> dmvolod@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
>
Re: gRPC and Google Guava version
Posted by Andrea Cosentino <an...@yahoo.com.INVALID>.
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: ancosen1985@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Monday, June 18, 2018, 8:55:37 AM GMT+2, Dmitry Volodin <dm...@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