Hi Wayne
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=437107
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.
Regards
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.
Thoughts?
Wayne
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
