1 <?xml version="1.0" encoding="UTF-8"?> 2 <!-- You may freely edit this file. See commented blocks below for --> 3 <!-- some examples of how to customize the build. --> 4 <!-- (If you delete it and reopen the project it will be recreated.) --> 5 <!-- By default, only the Clean and Build commands use this build script. --> 6 <!-- Commands such as Run, Debug, and Test only use this build script if --> 7 <!-- the Compile on Save feature is turned off for the project. --> 8 <!-- You can turn off the Compile on Save (or Deploy on Save) setting --> 9 <!-- in the project's Project Properties dialog box.--> 10 <project name="SceneBuilderKit" default="default" basedir="."> 11 <description>Builds, tests, and runs the project SceneBuilderKit.</description> 12 <property name="platforms.JDK_1.8.home" location="${java.home}/../"/> 13 <import file="nbproject/build-impl.xml"/> 14 <!-- 15 16 There exist several targets which are by default empty and which can be 17 used for execution of your tasks. These targets are usually executed 18 before and after some main targets. They are: 19 20 -pre-init: called before initialization of project properties 21 -post-init: called after initialization of project properties 22 -pre-compile: called before javac compilation 23 -post-compile: called after javac compilation 24 -pre-compile-single: called before javac compilation of single file 25 -post-compile-single: called after javac compilation of single file 26 -pre-compile-test: called before javac compilation of JUnit tests 27 -post-compile-test: called after javac compilation of JUnit tests 28 -pre-compile-test-single: called before javac compilation of single JUnit test 29 -post-compile-test-single: called after javac compilation of single JUunit test 30 -pre-jar: called before JAR building 31 -post-jar: called after JAR building 32 -post-clean: called after cleaning build products 33 34 (Targets beginning with '-' are not intended to be called on their own.) 35 36 Example of inserting an obfuscator after compilation could look like this: 37 38 <target name="-post-compile"> 39 <obfuscate> 40 <fileset dir="${build.classes.dir}"/> 41 </obfuscate> 42 </target> 43 44 For list of available properties check the imported 45 nbproject/build-impl.xml file. 46 47 48 Another way to customize the build is by overriding existing main targets. 49 The targets of interest are: 50 51 -init-macrodef-javac: defines macro for javac compilation 52 -init-macrodef-junit: defines macro for junit execution 53 -init-macrodef-debug: defines macro for class debugging 54 -init-macrodef-java: defines macro for class execution 55 -do-jar: JAR building 56 run: execution of project 57 -javadoc-build: Javadoc generation 58 test-report: JUnit report generation 59 60 An example of overriding the target for project execution could look like this: 61 62 <target name="run" depends="SceneBuilderKit-impl.jar"> 63 <exec dir="bin" executable="launcher.exe"> 64 <arg file="${dist.jar}"/> 65 </exec> 66 </target> 67 68 Notice that the overridden target depends on the jar target and not only on 69 the compile target as the regular run target does. Again, for a list of available 70 properties which you can use, check the target you are overriding in the 71 nbproject/build-impl.xml file. 72 73 --> 74 </project>