1<?xml version="1.0" encoding="UTF-8"?>
2<!--***********************************************************
3 *
4 * Licensed to the Apache Software Foundation (ASF) under one
5 * or more contributor license agreements.  See the NOTICE file
6 * distributed with this work for additional information
7 * regarding copyright ownership.  The ASF licenses this file
8 * to you under the Apache License, Version 2.0 (the
9 * "License"); you may not use this file except in compliance
10 * with the License.  You may obtain a copy of the License at
11 *
12 *   http://www.apache.org/licenses/LICENSE-2.0
13 *
14 * Unless required by applicable law or agreed to in writing,
15 * software distributed under the License is distributed on an
16 * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
17 * KIND, either express or implied.  See the License for the
18 * specific language governing permissions and limitations
19 * under the License.
20 *
21 ***********************************************************-->
22<!-- You may freely edit this file. See commented blocks below for -->
23<!-- some examples of how to customize the build. -->
24<!-- (If you delete it and reopen the project it will be recreated.) -->
25<!-- By default, only the Clean and Build commands use this build script. -->
26<!-- Commands such as Run, Debug, and Test only use this build script if -->
27<!-- the Compile on Save feature is turned off for the project. -->
28<!-- You can turn off the Compile on Save (or Deploy on Save) setting -->
29<!-- in the project's Project Properties dialog box.-->
30<project name="httpserv" default="default" basedir=".">
31    <description>Builds, tests, and runs the project httpserv.</description>
32    <import file="nbproject/build-impl.xml"/>
33    <!--
34
35    There exist several targets which are by default empty and which can be
36    used for execution of your tasks. These targets are usually executed
37    before and after some main targets. They are:
38
39      -pre-init:                 called before initialization of project properties
40      -post-init:                called after initialization of project properties
41      -pre-compile:              called before javac compilation
42      -post-compile:             called after javac compilation
43      -pre-compile-single:       called before javac compilation of single file
44      -post-compile-single:      called after javac compilation of single file
45      -pre-compile-test:         called before javac compilation of JUnit tests
46      -post-compile-test:        called after javac compilation of JUnit tests
47      -pre-compile-test-single:  called before javac compilation of single JUnit test
48      -post-compile-test-single: called after javac compilation of single JUunit test
49      -pre-jar:                  called before JAR building
50      -post-jar:                 called after JAR building
51      -post-clean:               called after cleaning build products
52
53    (Targets beginning with '-' are not intended to be called on their own.)
54
55    Example of inserting an obfuscator after compilation could look like this:
56
57        <target name="-post-compile">
58            <obfuscate>
59                <fileset dir="${build.classes.dir}"/>
60            </obfuscate>
61        </target>
62
63    For list of available properties check the imported
64    nbproject/build-impl.xml file.
65
66
67    Another way to customize the build is by overriding existing main targets.
68    The targets of interest are:
69
70      -init-macrodef-javac:     defines macro for javac compilation
71      -init-macrodef-junit:     defines macro for junit execution
72      -init-macrodef-debug:     defines macro for class debugging
73      -init-macrodef-java:      defines macro for class execution
74      -do-jar-with-manifest:    JAR building (if you are using a manifest)
75      -do-jar-without-manifest: JAR building (if you are not using a manifest)
76      run:                      execution of project
77      -javadoc-build:           Javadoc generation
78      test-report:              JUnit report generation
79
80    An example of overriding the target for project execution could look like this:
81
82        <target name="run" depends="httpserv-impl.jar">
83            <exec dir="bin" executable="launcher.exe">
84                <arg file="${dist.jar}"/>
85            </exec>
86        </target>
87
88    Notice that the overridden target depends on the jar target and not only on
89    the compile target as the regular run target does. Again, for a list of available
90    properties which you can use, check the target you are overriding in the
91    nbproject/build-impl.xml file.
92
93    -->
94</project>
95