japod@25: <?xml version="1.0" encoding="UTF-8"?>
japod@25: <!-- You may freely edit this file. See commented blocks below for -->
japod@25: <!-- some examples of how to customize the build. -->
japod@25: <!-- (If you delete it and reopen the project it will be recreated.) -->
japod@25: <project name="currency" default="default" basedir=".">
japod@25:     <description>Builds, tests, and runs the project.</description>
japod@25:     <import file="nbproject/build-impl.xml"/>
japod@25:     <!--
japod@25: 
japod@25:     There exist several targets which are by default empty and which can be 
japod@25:     used for execution of your tasks. These targets are usually executed 
japod@25:     before and after some main targets. They are: 
japod@25: 
japod@25:       -pre-init:                 called before initialization of project properties
japod@25:       -post-init:                called after initialization of project properties
japod@25:       -pre-compile:              called before javac compilation
japod@25:       -post-compile:             called after javac compilation
japod@25:       -pre-compile-single:       called before javac compilation of single file
japod@25:       -post-compile-single:      called after javac compilation of single file
japod@25:       -pre-compile-test:         called before javac compilation of JUnit tests
japod@25:       -post-compile-test:        called after javac compilation of JUnit tests
japod@25:       -pre-compile-test-single:  called before javac compilation of single JUnit test
japod@25:       -post-compile-test-single: called after javac compilation of single JUunit test
japod@25:       -pre-jar:                  called before JAR building
japod@25:       -post-jar:                 called after JAR building
japod@25:       -post-clean:               called after cleaning build products
japod@25: 
japod@25:     (Targets beginning with '-' are not intended to be called on their own.)
japod@25: 
japod@25:     Example of inserting an obfuscator after compilation could look like this:
japod@25: 
japod@25:         <target name="-post-compile">
japod@25:             <obfuscate>
japod@25:                 <fileset dir="${build.classes.dir}"/>
japod@25:             </obfuscate>
japod@25:         </target>
japod@25: 
japod@25:     For list of available properties check the imported 
japod@25:     nbproject/build-impl.xml file. 
japod@25: 
japod@25: 
japod@25:     Another way to customize the build is by overriding existing main targets.
japod@25:     The targets of interest are: 
japod@25: 
japod@25:       -init-macrodef-javac:     defines macro for javac compilation
japod@25:       -init-macrodef-junit:     defines macro for junit execution
japod@25:       -init-macrodef-debug:     defines macro for class debugging
japod@25:       -init-macrodef-java:      defines macro for class execution
japod@25:       -do-jar-with-manifest:    JAR building (if you are using a manifest)
japod@25:       -do-jar-without-manifest: JAR building (if you are not using a manifest)
japod@25:       run:                      execution of project 
japod@25:       -javadoc-build:           Javadoc generation
japod@25:       test-report:              JUnit report generation
japod@25: 
japod@25:     An example of overriding the target for project execution could look like this:
japod@25: 
japod@25:         <target name="run" depends="currency-impl.jar">
japod@25:             <exec dir="bin" executable="launcher.exe">
japod@25:                 <arg file="${dist.jar}"/>
japod@25:             </exec>
japod@25:         </target>
japod@25: 
japod@25:     Notice that the overridden target depends on the jar target and not only on 
japod@25:     the compile target as the regular run target does. Again, for a list of available 
japod@25:     properties which you can use, check the target you are overriding in the
japod@25:     nbproject/build-impl.xml file. 
japod@25: 
japod@25:     -->
japod@25: </project>