* Removed old and obsolete ant infrastructure. Developers are now required to

have their own ant installed.
* Rename README to README.txt and bring it up to date.
This commit is contained in:
hns 2007-02-08 09:26:42 +00:00
parent b1a958a394
commit d23d0af914
6 changed files with 8 additions and 110 deletions

View file

@ -1,52 +1,29 @@
This is the README file for the Helma build files as part of the Helma Object Publisher.
The build directory consists of the following files:
ant.jar
build.bat
build.sh
build.xml
crimson.jar
jaxp.jar
README
PREREQUISITES
=============
The Helma build script is using a software called Ant. Ant is a build system that was developed for the Jakarta Tomcat project. For more information about Ant, see <http://jakarta.apache.org/ant/>.
The Helma build script is uses Apache Ant.
For more information about Ant, see <http://ant.apache.org/>.
To run Ant, you also need JDK 1.3 or higher <http://java.sun.com/j2se/>.
For checking out the source files from Helma's CVS you also need a local installation of a CVS command-line client. More information about CVS at <http://www.cvshome.org/>.
For checking out the source files from Helma's CVS you also need a CVS client.
More information about CVS at <http://www.cvshome.org/>.
STARTING BUILD
==============
The build system is started by invoking the shell script appropriate to your platform, ie. build.sh for *nix (Linux, NetBSD etc.) and build.bat for Windows systems. You need to modify the script and set the JAVA_HOME to fit your system.
The build system is started by invoking the shell script appropriate to your
platform, ie. build.sh for *nix (Linux, NetBSD etc.) and build.bat for Windows
systems. You need to modify the script and set the JAVA_HOME to fit your system.
The generic syntax is
./build target
ant target
The parameter "target" specifies one of the build targets listed below.
BUILD A SNAPSHOT
================
To build a helma.jar with the most up-to-date version of helma yourself you need to run
./build checkout
and
./build snapshot
BUILD TARGETS
=============

Binary file not shown.

View file

@ -1,48 +0,0 @@
@echo off
set TARGET=%1%
REM set JAVA_HOME=c:\programme\jdk13
REM --------------------------------------------
REM No need to edit anything past here
REM --------------------------------------------
set BUILDFILE=build.xml
if "%TARGET%" == "" goto setdist
goto cont1
:cont1
if not "%2%" == "" goto setapp
goto final
:setdist
set TARGET=usage
goto cont1
:setapp
set APPNAME=-Dapplication=%2%
goto final
:final
if "%JAVA_HOME%" == "" goto javahomeerror
set CP=%CLASSPATH%;ant.jar;jaxp.jar;crimson.jar
if exist "%JAVA_HOME%\lib\tools.jar" set CP=%CP%;%JAVA_HOME%\lib\tools.jar
echo Classpath: "%CP%"
echo JAVA_HOME: "%JAVA_HOME%"
"%JAVA_HOME%\bin\java.exe" -classpath "%CP%" %APPNAME% org.apache.tools.ant.Main -buildfile %BUILDFILE% %TARGET%
goto end
REM -----------ERROR-------------
:javahomeerror
echo "ERROR: JAVA_HOME not found in your environment."
echo "Please, set the JAVA_HOME variable in your environment to match the"
echo "location of the Java Virtual Machine you want to use."
:end

View file

@ -1,31 +0,0 @@
#!/bin/sh
# export JAVA_HOME=/usr/lib/j2sdk1.4.0
#--------------------------------------------
# No need to edit anything past here
#--------------------------------------------
if test -z "${JAVA_HOME}" ; then
echo "ERROR: JAVA_HOME not found in your environment."
echo "Please, set the JAVA_HOME variable in your environment to match the"
echo "location of the Java Virtual Machine you want to use."
exit
fi
if test -f ${JAVA_HOME}/lib/tools.jar ; then
CLASSPATH=${CLASSPATH}:${JAVA_HOME}/lib/tools.jar
fi
if test -n "${2}" ; then
APPNAME=-Dapplication=${2}
fi
CP=${CLASSPATH}:ant.jar:jaxp.jar:../lib/crimson.jar
echo "Classpath: ${CP}"
echo "JAVA_HOME: ${JAVA_HOME}"
BUILDFILE=build.xml
${JAVA_HOME}/bin/java -classpath ${CP} ${APPNAME} org.apache.tools.ant.Main -buildfile ${BUILDFILE} ${1}

Binary file not shown.

Binary file not shown.