Files
vilya/etc/libs-incl.xml
T
Michael Bayne 39b21ef6d6 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/vilya/trunk@903 c613c5cb-e716-0410-b11b-feb51c14d237
2010-03-16 23:53:10 +00:00

36 lines
1.3 KiB
XML

<?xml version="1.0"?>
<!-- declares the libraries needed to build vilya -->
<project name="library-dependencies">
<fileset dir="${libs.dir}" id="vilya.libs">
<!-- Java dependencies -->
<include name="commons-digester.jar"/>
<include name="commons-logging.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="flexTasks.jar"/>
<include name="asc.jar"/>
<!-- these might be named lib-SNAPSHOT-0.0.jar or lib.jar -->
<include name="samskivert*.jar"/>
<include name="depot*.jar"/>
<include name="narya-base*.jar"/>
<include name="narya-distrib*.jar"/>
<include name="narya-tests*.jar"/>
<include name="narya-tools*.jar"/>
<include name="nenya-cast*.jar"/>
<include name="nenya-media*.jar"/>
<include name="nenya-miso*.jar"/>
<include name="nenya-rsrc*.jar"/>
<!-- ActionScript dependencies -->
<include name="ooolib*.swc"/>
<include name="naryalib*.swc"/>
<include name="nenyalib*.swc"/>
<!-- Thane dependencies -->
<include name="thane*.abc"/>
<include name="tamarin-builtin*.abc"/>
<include name="narya-abc*.abc"/>
</fileset>
</project>