> On 14 Mar 2017, at 14:34, Ed Willink <e...@willink.me.uk> wrote: > Please read the Bugzillas. > https://bugs.eclipse.org/bugs/show_bug.cgi?id=427862 > <https://bugs.eclipse.org/bugs/show_bug.cgi?id=427862> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=437107 > <https://bugs.eclipse.org/bugs/show_bug.cgi?id=437107>Both bugs are assigned > to nobody and in the Cross-Project component. I'm not sure who is > responsible. However, it seems impossible to address them as there is no > clear path to decide on. It looks like their main purpose is a sink for > discussions. I'd suggest closing them as WONTFIX. It doesn't look like > they'll ever be solved.
> The problem never occurs for individual projects. It only occurs when an > integrating project 'inherits' conflicting Guava loads from two distinct > component projects with Guava in the APIs. > > So Mylyn only is no problem, but something that integrates Mylyn and Xtext > can encounter obscure failures when the wrong class is re-used on a code path > in which both are used. > FWIW, there are technical solutions to allow projects to co-exist consuming different versions of Guava. Yes it is complicated and gets even more complicated when projects are re-exporting Guava as part of their APIs. But there are solutions that work. If you believer there are specific problems with regards to the Guava libraries in Orbit please open a bug for Orbit with more details (eg., exceptions). We'll look at addressing them. -Gunnar
_______________________________________________ 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
