From c77ff811604d50c5ac550596e127bb84be1c0d0c Mon Sep 17 00:00:00 2001
From: Michael Bayne <mdb@threerings.net>
Date: Tue, 16 Mar 2010 23:52:58 +0000
Subject: [PATCH] Should be no harm in compiling against Guava instead of GC as
 they have the exact same API. So if you ship with GC instead of Guava,
 nothing will break.

Eventually we'll want to ship with Guava instead of GC so that we can use
Guava-specific methods, but projects can make that switch at their leisure.


git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@6044 542714f4-19e9-0310-aa3c-eee0fc999fb1
---
 build.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/build.xml b/build.xml
index cfbac6004..f7b5fd029 100644
--- a/build.xml
+++ b/build.xml
@@ -207,7 +207,7 @@
       <zipfileset src="${deploy.dir}/lib/samskivert.jar"/>
       <zipfileset src="${deploy.dir}/lib/velocity-1.5-dev.jar"/>
       <zipfileset src="${deploy.dir}/lib/javassist.jar"/>
-      <zipfileset src="${deploy.dir}/lib/google-collect.jar"/>
+      <zipfileset src="${deploy.dir}/lib/guava.jar"/>
       <zipfileset src="${deploy.dir}/lib/commons-collections.jar"/>
     </jar>
     <jar destfile="${deploy.dir}/${lib.name}-tests.jar">