Re: Guava artifact version issues

2012-09-24 Thread Thomas Broyer
On Mon, Sep 24, 2012 at 5:24 PM, Eric Czech wrote: > Thanks Ron but no unfortunately, they're not upwards compatible. > Entire classes are renamed or removed in later versions so artifacts > using the old version definitely can't just use the new one. Only for @Beta classes/methods (which you sho

Re: Guava artifact version issues

2012-09-24 Thread Ron Wheeler
On 24/09/2012 11:24 AM, Eric Czech wrote: Thanks Ron but no unfortunately, they're not upwards compatible. Entire classes are renamed or removed in later versions so artifacts using the old version definitely can't just use the new one. Having our own guava artifact with the code from 13.0.1 mea

Re: Guava artifact version issues

2012-09-24 Thread Eric Czech
Thanks Ron but no unfortunately, they're not upwards compatible. Entire classes are renamed or removed in later versions so artifacts using the old version definitely can't just use the new one. Having our own guava artifact with the code from 13.0.1 means that we can use that version *internally*

Re: Guava artifact version issues

2012-09-24 Thread Ron Wheeler
Is there no upward compatibility? Can projects A and B execute using Guava 13.0.1? Usually, you just exclude the lower versions in the dependency specification for the third party library and run with the highest version. If Guava is not upwards compatible and the third party libraries use di

Re: Guava artifact version issues

2012-09-24 Thread Stephen Connolly
shade via intermediate modules On 24 September 2012 14:36, Eric Czech wrote: > Thank you, that's exactly what I was looking for. > > Is there a way to shade versions of an artifact in a particular way? > For example, if projects A and B depend on Guava r09 and projects C > and D depend on Guava

Re: Guava artifact version issues

2012-09-24 Thread Eric Czech
Thank you, that's exactly what I was looking for. Is there a way to shade versions of an artifact in a particular way? For example, if projects A and B depend on Guava r09 and projects C and D depend on Guava 13.0.1, how can I make sure that each is referencing the correctly shaded version when th

Re: Guava artifact version issues

2012-09-24 Thread Stephen Connolly
Maven shade plugin can relocate all the classes into a different package for you in minutes of config and seconds of build time On 24 September 2012 13:43, Eric Czech wrote: > Hi everyone, > > I'm continually running into issues with Guava dependencies where the > version of Guava we use is inco