Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Is it time to update to Guava 18?

Hi Wayne


The Luna experience was that in the absence of tooling, all projects MUST use the same Guava, which should be the latest in Orbit.

Mixed Guava is a disaster. So far nobody seems to have moved for Mars.

If we are to move, I think we should all aim to move in I-builds immediately following M6.

There may be a maintenance issue. e.g. Xtext 2.8.0 is out,so moving to Guava 18 might force a 2.9.0.

I feel that barely a day before M6 is too late to request this.


        Ed Willink

On 20/03/2015 21:34, Wayne Beaton wrote:
The Buildship (Eclipse Plug-ins for Grade) project should be joining Mars soon. They're using Guava 18, which has already been approved by the IP Team. I believe that m2e has designs on it as well.

Can those projects that are currently using Guava 15 update to version 18?

More generally, I think that we need a policy for these widely-shared libraries. Intuitively, it makes sense to me that we should try to use the most recent version released in Orbit with the simultaneous release.



Back to the top