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

@@ -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">