Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Guava 15/21 warning

On 14 Mar 2017, at 14:34, Ed Willink <ed@xxxxxxxxxxxxx> wrote:
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.


Back to the top