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