| [mdt-papyrus.dev] Fwd: [cross-project-issues-dev] Guava 15/21 warning |
|
Hi Benoit You should be subscribed to cross-project-dev where I posted the message below with Bugzilla references. Bottom line: you have two choices. a) Ideally you persuade all relevant Eclipse projects to include
accurate "uses" directives for Guava. Since there is no tooling
for this, it is really hard. I do not even know how to do it for
OCL. b) You persuade all relevant Eclipse projects to include Guava 21 within their dependency range so that in practice Papyrus is single version. OCL does not specify any Guava version bounds since it re-uses
Guava solely via Xtext to which the choice is delegated. If you
use Guava 21 you need the latest OCL N-build to avoid use of a
removed method. NB. Particular challenges occur if Guava appears in APIs, Therefore it is VERY important that e.g. Optional and MultiMap are not used in interfaces. Regards Ed Willink -------- Forwarded Message --------
Hi We have been using Guava 15 for some time. The latest Mylyn snapshot (mylyn-3.22.0.v20170308-0427.zip) has moved to Guava 21. When we changed to Guava 15 for Luna, it was all rather painful: https://bugs.eclipse.org/bugs/show_bug.cgi?id=427862 https://bugs.eclipse.org/bugs/show_bug.cgi?id=437107 is open to identify a policy for non-singleton plugins, but no resolution has been found. We can probably avoid problems if we all move to Guava 21 for M7 and if Mylyn refrains from contributing its change at M6. Regards Ed Willink --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
|