Re: [cross-project-issues-dev] Is it time to update to Guava 18?

Hi If you think Guava 18 is a good idea for Neon, I suggest starting to make a lot of noise at M1 so that most projects migrate for M2. Regards Ed Willink On 25/05/2015 18:10, Sam Davis wrote: Hi, Looking in releases/mars/201505221000/plugins/ I see only Guava 15. If I underst

Re: [cross-project-issues-dev] Is it time to update to Guava 18?

Hi, Looking in releases/mars/201505221000/plugins/ I see only Guava 15. If I understand the process correctly, each project updating to Guava 18 would have to file a CQ, and the deadline to do so for Mars was in February, so I guess we're sticking with Guava 15 for Mars? Cheers, Sam -- Sam Dav

Re: [cross-project-issues-dev] Is it time to update to Guava 18?

Hi guys, I’ve filled a bug over RCPTT to update guava to at least 15: https://bugs.eclipse.org/bugs/show_bug.cgi?id=466770. Best regards, Andrey. > On 8 мая 2015 г., at 0:06, Alexander Nyßen wrote: > > Should we raise a bug against RCPTT then? As we know from past experience, > mixing diff

Re: [cross-project-issues-dev] Is it time to update to Guava 18?

Should we raise a bug against RCPTT then? As we know from past experience, mixing different Guava versions might be harmful. Cheers Alexander Von meinem iPhone gesendet > Am 07.05.2015 um 12:35 schrieb Pierre-Charles David > : > > Le 07/05/2015 09:16, Alexander Nyßen a écrit : >> Hi, >> >>

Re: [cross-project-issues-dev] Is it time to update to Guava 18?

Le 07/05/2015 09:16, Alexander Nyßen a écrit : Hi, I am not sure if this actually is a problem, but it might be something to watch: If I interpret the latest unique version repo reports (http://download.eclipse.org/releases/staging/buildInfo/reporeports/reports/nonUniqueVersions.txt) correctl

Re: [cross-project-issues-dev] Is it time to update to Guava 18?

Hi, I am not sure if this actually is a problem, but it might be something to watch: If I interpret the latest unique version repo reports (http://download.eclipse.org/releases/staging/buildInfo/reporeports/reports/nonUniqueVersions.txt

Re: [cross-project-issues-dev] Is it time to update to Guava 18?

Hi My specific interests are OCL and QVTd that depend on Xtext that uses Guava, so I have no problem, but my users do. 'SimRel products' that would need to recode for Mars under your policy are at least Papyrus and probably BIRT. One of Eclipse's good features is that you can just create an

Re: [cross-project-issues-dev] Is it time to update to Guava 18?

Hi Ed, > On 25/03/2015 10:24, Andreas Sewe wrote: >> Possibly, but being open to third-party plugins, we cannot prevent the >> presence of multiple Guava versions in general. >> >> Anyway, I think the burden is on the developers of integration bundles >> C. You *can* shield yourself from this prob

Re: [cross-project-issues-dev] Is it time to update to Guava 18?

HI On 25/03/2015 10:24, Andreas Sewe wrote: Possibly, but being open to third-party plugins, we cannot prevent the presence of multiple Guava versions in general. Anyway, I think the burden is on the developers of integration bundles C. You *can* shield yourself from this problem (A and B both

Re: [cross-project-issues-dev] Is it time to update to Guava 18?

Hi Ed, > The analysis is indeed unclear because nobody has invested the time to > debug the problem or solution. > > My best theory seems to be all that there is: > > The problem seems to arise for a project that integrates the Guava-based > facilities of A and the Guava-based facilities of B, a

Re: [cross-project-issues-dev] Is it time to update to Guava 18?

Hi The analysis is indeed unclear because nobody has invested the time to debug the problem or solution. My best theory seems to be all that there is: The problem seems to arise for a project that integrates the Guava-based facilities of A and the Guava-based facilities of B, and when a Guav

Re: [cross-project-issues-dev] Is it time to update to Guava 18?

Hi Ed, hi Wayne, > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=437107 in that bug report I frankly miss a clear analysis as to *why* different Guava bundles are a problem. Agreed, incorrect metadata is always a problem in OSGi, such as bundles exporting com.google.common packages without v

Re: [cross-project-issues-dev] Is it time to update to Guava 18?

Just to clarify, m2e is quite happy with guava 15 included in sim rel and we will need to validate if guava 18 breaks anything. m2e does plan to ship separate guava 18 as part of embedded maven runtime, but this copy is not exported to OSGi and should not interfere with guava used by other OSGi bu

Re: [cross-project-issues-dev] Is it time to update to Guava 18?

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 thi

[cross-project-issues-dev] Is it time to update to Guava 18?

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 thi