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@6043 542714f4-19e9-0310-aa3c-eee0fc999fb1
This commit is contained in:
+1
-1
@@ -9,8 +9,8 @@
|
||||
<include name="depot.jar"/>
|
||||
<include name="ehcache.jar"/>
|
||||
<include name="flexTasks.jar"/>
|
||||
<include name="guava.jar"/>
|
||||
<include name="guice.jar"/>
|
||||
<include name="google-collect.jar"/>
|
||||
<include name="javassist.jar"/>
|
||||
<include name="junit4.jar"/>
|
||||
<include name="retroweaver-all-1.2.2.jar"/>
|
||||
|
||||
Reference in New Issue
Block a user