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