#!/bin/sh

BUILD_HOME=`dirname $0`
cd $BUILD_HOME
BUILD_HOME=`pwd`

# build dir
cd /scratch/build

# this might be sufficient, however some libraries.ent chunks will fail,
# because the patches are produced against CVS version on 01-Feb-2005 ...
# Anyway, the portal will be build
[ -r jboss-portal-2.0-src.zip ] || \
wget http://mesh.dl.sourceforge.net/sourceforge/jboss/jboss-portal-2.0-src.zip
[ -d jboss-portal-2.0 ] && mv jboss-portal-2.0 jboss-portal-2.0.old
unzip -U jboss-portal-2.0-src.zip
cd jboss-portal-2.0

# every developer has ant - and we define: it has to be at least Version 1.6
# - no need to distribute it (otherwise one must consequently distribute
#   the jdk as well ;-)
rm -f tools/lib/{ant,bsf,crimson,optional,saxon,xalan,xercesImpl,xml-apis,}.jar
rm -rf tools/bin

# ant-contrib helps to be able to build against available libs in the AS
# using 'if' tasks - otherwise we would have to write a lot more
# targets/tests ... (linking againts AS libs enables one to reduces
# ressource usage on the server/to find incompats early).
# see http://sourceforge.net/projects/ant-contrib/
cd thirdparty
wget http://mesh.dl.sourceforge.net/sourceforge/ant-contrib/ant-contrib-1.0b1-bin.zip
unzip -U ant-contrib-1.0b1-bin.zip
rm -rf ant-contrib/docs ant-contrib-1.0b1-bin.zip
echo "Version: 1.0b1" >>ant-contrib/README.txt

cd ..

for p in  $BUILD_HOME/patches/*.patch ; do
	patch -p1 -b -z .orig < $p
done

cd build
ant

# build the setup.ddl files
cd ../core
ant ddl
cd ../forums
ant ddl