From 1.5.0 --> 1.5.1 there's another guava upgrade

[Nirmal Fernando]

Hi All,

Just a thought....

Wouldn't it be better if we can minimize frequent upgrades of dependency bundles? As users, doing these kind of frequent upgrades is pretty time consuming, if you have a large code base and lot of products (cause building with tests isn't enough, we need to do all sorts of functionality tests too ).

I had to go through this ones (had to upgrade our code base from guava 11 -> 12), It took around two working days to cover all sorts of tests. And seems like I've to go thru' that pain again to upgrade guava from 12 -> 13. :(

Any other solution?

--

Thanks & regards,
Nirmal

Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/

[Adrian Cole]

Hi, Nirmal.

What sort of additional testing are you referring to, which you wouldn't already be doing when upgrading something?  I imagine you have automated tests in CI; Do you have a different CI test suite for guava updates?

Also, what guava related problem did you encounter between 12 and 13?

There's a lot more difference between guava 11 and 12, than 12-13, which is why I'm asking.  I'd like to understand concretely what the reason is with guava 13, which causes you concern, or if you are just concerned that we update libraries as we see fit.

-A

--
You received this message because you are subscribed to the Google Groups "jclouds" group.
To post to this group, send email to jcl...@googlegroups.com.
To unsubscribe from this group, send email to jclouds+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jclouds?hl=en.

[Adrian Cole]

Ps.  We didn't change the major version of guava between 1.5.0 and 1.5.1.  In both cases, it is 13.0:

https://github.com/jclouds/jclouds/blob/jclouds-1.5.0/core/pom.xml

https://github.com/jclouds/jclouds/blob/jclouds-1.5.1/core/pom.xml

We will change to guava 14 in jclouds 1.6, though.

-A

[Nirmal Fernando]

Hi Adrian,

On Sat, Nov 3, 2012 at 11:00 PM, Adrian Cole <adrian...@gmail.com> wrote:

Hi, Nirmal.

What sort of additional testing are you referring to, which you wouldn't already be doing when upgrading something?

I didn't mean to say that we might want to do additional tests when upgrading guava, but since the fact that lot of other dependencies of our code, depends on guava and they might not still supports the latest version, we might run into trouble.

[Nirmal Fernando]

On Sat, Nov 3, 2012 at 11:09 PM, Adrian Cole <adrian...@gmail.com> wrote:

Ps.  We didn't change the major version of guava between 1.5.0 and 1.5.1.  In both cases, it is 13.0:

https://github.com/jclouds/jclouds/blob/jclouds-1.5.0/core/pom.xml

https://github.com/jclouds/jclouds/blob/jclouds-1.5.1/core/pom.xml

hm... ok... I just checked we were using 1.5.0-beta-5 and then Jclouds had Guava 12 dependency, isn't it?
 

[Adrian Cole]

On Nov 3, 2012 10:43 AM, "Nirmal Fernando" <nir...@wso2.com> wrote:
>
> Hi Adrian,
>
> On Sat, Nov 3, 2012 at 11:00 PM, Adrian Cole <adrian...@gmail.com> wrote:
>>
>> Hi, Nirmal.
>>
>> What sort of additional testing are you referring to, which you wouldn't already be doing when upgrading something?
>
> I didn't mean to say that we might want to do additional tests when upgrading guava, but since the fact that lot of other dependencies of our code, depends on guava and they might not still supports the latest version, we might run into trouble.

Ok. So for now, we could focus on only bumping subminor guava on subminor jclouds.  In that case, it shouldn't be as risky at face value, right?  Since guava 14 isnt out, we can avoid pulling that into jclouds 1.5.x and instead prepare for a sooner 1.6 :)

[Adrian Cole]

Right, we didn't finalize the deps for jclouds 1.5 when it was beta.  In fact, you'll have noticed we took a long time getting out of beta.. a few months.  Hopefully, we won't repeat that :)

[Nirmal Fernando]

On Sat, Nov 3, 2012 at 11:18 PM, Adrian Cole <adrian...@gmail.com> wrote:

On Nov 3, 2012 10:43 AM, "Nirmal Fernando" <nir...@wso2.com> wrote:
>
> Hi Adrian,
>
> On Sat, Nov 3, 2012 at 11:00 PM, Adrian Cole <adrian...@gmail.com> wrote:
>>
>> Hi, Nirmal.
>>
>> What sort of additional testing are you referring to, which you wouldn't already be doing when upgrading something?
>
> I didn't mean to say that we might want to do additional tests when upgrading guava, but since the fact that lot of other dependencies of our code, depends on guava and they might not still supports the latest version, we might run into trouble.

Ok. So for now, we could focus on only bumping subminor guava on subminor jclouds. 

+1
 

--
You received this message because you are subscribed to the Google Groups "jclouds-dev" group.
To post to this group, send email to jclou...@googlegroups.com.
To unsubscribe from this group, send email to jclouds-dev...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jclouds-dev?hl=en.

[Nirmal Fernando]

On Sat, Nov 3, 2012 at 11:19 PM, Adrian Cole <adrian...@gmail.com> wrote:

Right, we didn't finalize the deps for jclouds 1.5 when it was beta.  In fact, you'll have noticed we took a long time getting out of beta.. a few months.  Hopefully, we won't repeat that :)

Great :-)
 

[Nirmal Fernando]

Adrian,

Could you please tell me in which 1.5.0-beta, you all upgraded to guava 13 ?