build.xml revision 0
0N/A<?
xml version="1.0" encoding="UTF-8"?>
0N/A Copyright 2002-2007 Sun Microsystems, Inc. All Rights Reserved. 0N/A DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER. 0N/A This code is free software; you can redistribute it and/or modify it 0N/A under the terms of the GNU General Public License version 2 only, as 0N/A published by the Free Software Foundation. 0N/A This code is distributed in the hope that it will be useful, but WITHOUT 0N/A ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or 0N/A FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License 0N/A version 2 for more details (a copy is included in the LICENSE file that 0N/A accompanied this code). 0N/A You should have received a copy of the GNU General Public License version 0N/A 2 along with this work; if not, write to the Free Software Foundation, 0N/A Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. 0N/A Please contact Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, 0N/A CA 95054 USA or visit www.sun.com if you need additional information or 0N/A<!-- This is an Ant project file. Ant is a build tool like make or gnumake which is not 0N/A dependent on the underlying OS shell. For more information on Ant, please see 0N/A<!-- A "project" describes a set of targets that may be requested 0N/A when Ant is executed. The "default" attribute defines the 0N/A target which is executed if no specific target is requested, 0N/A and the "basedir" attribute defines the current working directory 0N/A from which Ant executes the requested task. This is normally 0N/A set to the current working directory. 0N/A<
project name="HotSpot Serviceability Agent" default="all" basedir=".">
0N/A <!-- Property Definitions --> 0N/A<!-- The "prepare" target is used to construct the deployment home 0N/A directory structure (if necessary), and to copy in static files 0N/A as required. In the example below, Ant is instructed to create 0N/A the deployment directory, copy the contents of the "web/" source 0N/A hierarchy, and set up the WEB-INF subdirectory appropriately. 0N/A <
target name="prepare">
0N/A <
mkdir dir="${classes}"/>
0N/A<!-- The "clean" target removes the deployment home directory structure, 0N/A so that the next time the "compile" target is requested, it will need 0N/A to compile everything from scratch. 0N/A <
target name="clean">
0N/A <
delete dir="${classes}"/>
0N/A<!-- The "compile" target is used to compile (or recompile) the Java classes 0N/A that make up this web application. The recommended source code directory 0N/A structure makes this very easy because the <javac> task automatically 0N/A works its way down a source code hierarchy and compiles any class that 0N/A has not yet been compiled, or where the source file is newer than the 0N/A Feel free to adjust the compilation option parameters (debug, 0N/A optimize, and deprecation) to suit your requirements. It is also 0N/A possible to base them on properties, so that you can adjust this 0N/A behavior at runtime. 0N/A The "compile" task depends on the "prepare" task, so the deployment 0N/A home directory structure will be created if needed the first time. 0N/A <
target name="compile" depends="prepare" description="Compiles the sources">
0N/A destdir="${classes}" 0N/A debug="on" deprecation="on" 0N/A <
target name="deploy" depends="compile" description="Creates a deployment bundle">
0N/A basedir="${classes}"/>
0N/A <
target name="all" depends="deploy" description="Builds sources and deployment jar"/>