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