1 <?xml version="1.0" encoding="UTF-8"?><!-- You may freely edit this file. See commented blocks below for --><!-- some examples of how to customize the build. --><!-- (If you delete it and reopen the project it will be recreated.) --><!-- By default, only the Clean and Build commands use this build script. --><!-- Commands such as Run, Debug, and Test only use this build script if --><!-- the Compile on Save feature is turned off for the project. --><!-- You can turn off the Compile on Save (or Deploy on Save) setting --><!-- in the project's Project Properties dialog box.--><project name="NicoBrowser" default="default" basedir=".">
\r
2 <description>Builds, tests, and runs the project NicoBrowser.</description>
\r
3 <import file="nbproject/build-impl.xml"/>
\r
6 There exist several targets which are by default empty and which can be
\r
7 used for execution of your tasks. These targets are usually executed
\r
8 before and after some main targets. They are:
\r
10 -pre-init: called before initialization of project properties
\r
11 -post-init: called after initialization of project properties
\r
12 -pre-compile: called before javac compilation
\r
13 -post-compile: called after javac compilation
\r
14 -pre-compile-single: called before javac compilation of single file
\r
15 -post-compile-single: called after javac compilation of single file
\r
16 -pre-compile-test: called before javac compilation of JUnit tests
\r
17 -post-compile-test: called after javac compilation of JUnit tests
\r
18 -pre-compile-test-single: called before javac compilation of single JUnit test
\r
19 -post-compile-test-single: called after javac compilation of single JUunit test
\r
20 -pre-jar: called before JAR building
\r
21 -post-jar: called after JAR building
\r
22 -post-clean: called after cleaning build products
\r
24 (Targets beginning with '-' are not intended to be called on their own.)
\r
26 Example of inserting an obfuscator after compilation could look like this:
\r
28 <target name="-post-compile">
\r
30 <fileset dir="${build.classes.dir}"/>
\r
34 For list of available properties check the imported
\r
35 nbproject/build-impl.xml file.
\r
38 Another way to customize the build is by overriding existing main targets.
\r
39 The targets of interest are:
\r
41 -init-macrodef-javac: defines macro for javac compilation
\r
42 -init-macrodef-junit: defines macro for junit execution
\r
43 -init-macrodef-debug: defines macro for class debugging
\r
44 -init-macrodef-java: defines macro for class execution
\r
45 -do-jar-with-manifest: JAR building (if you are using a manifest)
\r
46 -do-jar-without-manifest: JAR building (if you are not using a manifest)
\r
47 run: execution of project
\r
48 -javadoc-build: Javadoc generation
\r
49 test-report: JUnit report generation
\r
51 An example of overriding the target for project execution could look like this:
\r
53 <target name="run" depends="NicoBrowser-impl.jar">
\r
54 <exec dir="bin" executable="launcher.exe">
\r
55 <arg file="${dist.jar}"/>
\r
59 Notice that the overridden target depends on the jar target and not only on
\r
60 the compile target as the regular run target does. Again, for a list of available
\r
61 properties which you can use, check the target you are overriding in the
\r
62 nbproject/build-impl.xml file.
\r