Re: [cross-project-issues-dev] Is it acceptable to have two com.google.common.collect providers?
I've opened bug 371396 in orbit to discuss/decide.
From: Ed Willink <ed@xxxxxxxxxxxxx>
Date: 02/13/2012 11:59 AM
Subject: Re: [cross-project-issues-dev] Is it acceptable to have two
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
The story is clear. Does that mean com.google.collect should be removed
from Orbit, or just carefully excluded from Orbit for Simultaneous
On 13/02/2012 14:55, Brian de Alwis wrote:
> On 13-Feb-2012, at 7:57 AM, Paul Webster wrote:
>> Did Guava absorb com.google.collect, and that's why it includes those
packages (instead of consuming them from the next version of the
> Yep. From<http://code.google.com/p/google-collections/>:
>> This library was renamed to Guava!
>> What you see here is ancient and unmaintained. Do not use it.
>> Guava is a fully compatible superset of the old Google Collections
Library. It also includes years worth of bug fixes, doc fixes, and
performance fixes, so we strongly encourage you to use Guava instead of
>> If your application ever ends up with both google-collect-1.0.jar and
guava-r##.jar on the same classpath, simply remove the Google Collections
JAR and you should be fine. If you don't remove it, it will either cause
terrible problems (if it comes before guava in the classpath) or will never
even be seen anyway (if it comes after).
>> The project you're looking at now will not be maintained. We apologize
for any confusion this causes.
> cross-project-issues-dev mailing list
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.1913 / Virus Database: 2112/4806 - Release Date: 02/12/12
cross-project-issues-dev mailing list