franta-hg@0: <?xml version="1.0" encoding="UTF-8"?>
franta-hg@83: <!--
franta-hg@83:  SQL-DK
franta-hg@83:  Copyright © 2013 František Kučera (frantovo.cz)
franta-hg@83: 
franta-hg@83:  This program is free software: you can redistribute it and/or modify
franta-hg@83:  it under the terms of the GNU General Public License as published by
franta-hg@83:  the Free Software Foundation, either version 3 of the License, or
franta-hg@83:  (at your option) any later version.
franta-hg@83: 
franta-hg@83:  This program is distributed in the hope that it will be useful,
franta-hg@83:  but WITHOUT ANY WARRANTY; without even the implied warranty of
franta-hg@83:  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
franta-hg@83:  GNU General Public License for more details.
franta-hg@83: 
franta-hg@83:  You should have received a copy of the GNU General Public License
franta-hg@83:  along with this program. If not, see <http://www.gnu.org/licenses/>.
franta-hg@83: -->
franta-hg@83: 
franta-hg@0: <!-- You may freely edit this file. See commented blocks below for -->
franta-hg@0: <!-- some examples of how to customize the build. -->
franta-hg@0: <!-- (If you delete it and reopen the project it will be recreated.) -->
franta-hg@0: <!-- By default, only the Clean and Build commands use this build script. -->
franta-hg@0: <!-- Commands such as Run, Debug, and Test only use this build script if -->
franta-hg@0: <!-- the Compile on Save feature is turned off for the project. -->
franta-hg@0: <!-- You can turn off the Compile on Save (or Deploy on Save) setting -->
franta-hg@0: <!-- in the project's Project Properties dialog box.-->
franta-hg@0: <project name="sql-dk" default="default" basedir=".">
franta-hg@0:     <description>Builds, tests, and runs the project sql-dk.</description>
franta-hg@0:     <import file="nbproject/build-impl.xml"/>
franta-hg@0:     <!--
franta-hg@0: 
franta-hg@0:     There exist several targets which are by default empty and which can be 
franta-hg@0:     used for execution of your tasks. These targets are usually executed 
franta-hg@0:     before and after some main targets. They are: 
franta-hg@0: 
franta-hg@0:       -pre-init:                 called before initialization of project properties
franta-hg@0:       -post-init:                called after initialization of project properties
franta-hg@0:       -pre-compile:              called before javac compilation
franta-hg@0:       -post-compile:             called after javac compilation
franta-hg@0:       -pre-compile-single:       called before javac compilation of single file
franta-hg@0:       -post-compile-single:      called after javac compilation of single file
franta-hg@0:       -pre-compile-test:         called before javac compilation of JUnit tests
franta-hg@0:       -post-compile-test:        called after javac compilation of JUnit tests
franta-hg@0:       -pre-compile-test-single:  called before javac compilation of single JUnit test
franta-hg@0:       -post-compile-test-single: called after javac compilation of single JUunit test
franta-hg@0:       -pre-jar:                  called before JAR building
franta-hg@0:       -post-jar:                 called after JAR building
franta-hg@0:       -post-clean:               called after cleaning build products
franta-hg@0: 
franta-hg@0:     (Targets beginning with '-' are not intended to be called on their own.)
franta-hg@0: 
franta-hg@0:     Example of inserting an obfuscator after compilation could look like this:
franta-hg@0: 
franta-hg@0:         <target name="-post-compile">
franta-hg@0:             <obfuscate>
franta-hg@0:                 <fileset dir="${build.classes.dir}"/>
franta-hg@0:             </obfuscate>
franta-hg@0:         </target>
franta-hg@0: 
franta-hg@0:     For list of available properties check the imported 
franta-hg@0:     nbproject/build-impl.xml file. 
franta-hg@0: 
franta-hg@0: 
franta-hg@0:     Another way to customize the build is by overriding existing main targets.
franta-hg@0:     The targets of interest are: 
franta-hg@0: 
franta-hg@0:       -init-macrodef-javac:     defines macro for javac compilation
franta-hg@0:       -init-macrodef-junit:     defines macro for junit execution
franta-hg@0:       -init-macrodef-debug:     defines macro for class debugging
franta-hg@0:       -init-macrodef-java:      defines macro for class execution
franta-hg@0:       -do-jar-with-manifest:    JAR building (if you are using a manifest)
franta-hg@0:       -do-jar-without-manifest: JAR building (if you are not using a manifest)
franta-hg@0:       run:                      execution of project 
franta-hg@0:       -javadoc-build:           Javadoc generation
franta-hg@0:       test-report:              JUnit report generation
franta-hg@0: 
franta-hg@0:     An example of overriding the target for project execution could look like this:
franta-hg@0: 
franta-hg@0:         <target name="run" depends="sql-dk-impl.jar">
franta-hg@0:             <exec dir="bin" executable="launcher.exe">
franta-hg@0:                 <arg file="${dist.jar}"/>
franta-hg@0:             </exec>
franta-hg@0:         </target>
franta-hg@0: 
franta-hg@0:     Notice that the overridden target depends on the jar target and not only on 
franta-hg@0:     the compile target as the regular run target does. Again, for a list of available 
franta-hg@0:     properties which you can use, check the target you are overriding in the
franta-hg@0:     nbproject/build-impl.xml file. 
franta-hg@0: 
franta-hg@18: 	-->
franta-hg@18: 	
franta-hg@18: 	<target name="-pre-compile">
franta-hg@18: 		<exec executable="./version-info.sh" output="data/info/globalcode/sql/dk/version.txt"/>
franta-hg@96: 		<exec executable="./help-generator.sh" output="data/info/globalcode/sql/dk/help.txt"/>
franta-hg@18: 	</target>
franta-hg@18: 	
franta-hg@81: 	<target name="-post-jar">
franta-hg@81: 		<exec executable="./bash-completion.sh" output="dist/bash-completion.sh"/>
franta-hg@81: 	</target>
franta-hg@81: 	
franta-hg@0: </project>