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