Files
nenya/etc/libs-incl.xml
T
Michael Bayne b260dbe768 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/nenya/trunk@905 ed5b42cb-e716-0410-a449-f6a68f950b19
2010-03-16 23:53:01 +00:00

41 lines
1.5 KiB
XML

<?xml version="1.0"?>
<!-- declares the libraries needed to build nenya -->
<project name="library-dependencies">
<fileset dir="${libs.dir}" id="nenya.libs">
<!-- Java dependencies -->
<include name="ant.jar"/>
<include name="commons-collections.jar"/>
<include name="commons-digester.jar"/>
<include name="commons-logging.jar"/>
<include name="commons-beanutils.jar"/>
<include name="guava.jar"/>
<include name="guice.jar"/>
<include name="junit4.jar"/>
<include name="retroweaver-all-1.2.2.jar"/>
<include name="xml-writer.jar"/>
<include name="javassist.jar"/>
<!-- these might be named lib-SNAPSHOT-0.0.jar or lib.jar -->
<include name="samskivert.jar"/>
<include name="narya-base*.jar"/>
<include name="narya-distrib*.jar"/>
<include name="narya-tools*.jar"/>
<!-- these LWJGL, JME and JME-BUI libraries are optional -->
<include name="lwjgl.jar"/>
<include name="lwjgl_util.jar"/>
<include name="jme-awt.jar"/>
<include name="jme-effects.jar"/>
<include name="jme-model.jar"/>
<include name="jme-sound.jar"/>
<include name="jme-terrain.jar"/>
<include name="jme.jar"/>
<include name="jme-bui.jar"/>
<include name="jogg-0.0.7.jar"/>
<include name="jorbis-0.0.15.jar"/>
<include name="jl1.0.jar"/>
<!-- ActionScript dependencies -->
<include name="ooolib*.swc"/>
<include name="naryalib*.swc"/>
<include name="flexlib*.swc"/>
</fileset>
</project>