| [2] | 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 | <project name="RouteGUI" default="default" basedir=".">
|
|---|
| 6 | <description>Builds, tests, and runs the project RouteGUI.</description>
|
|---|
| 7 | <import file="nbproject/build-impl.xml"/>
|
|---|
| 8 | <import file="nbproject/profiler-build-impl.xml"/>
|
|---|
| 9 | <import file="nbproject/profiler-build-impl.xml"/>
|
|---|
| 10 | <!--
|
|---|
| 11 |
|
|---|
| 12 | There exist several targets which are by default empty and which can be
|
|---|
| 13 | used for execution of your tasks. These targets are usually executed
|
|---|
| 14 | before and after some main targets. They are:
|
|---|
| 15 |
|
|---|
| 16 | -pre-init: called before initialization of project properties
|
|---|
| 17 | -post-init: called after initialization of project properties
|
|---|
| 18 | -pre-compile: called before javac compilation
|
|---|
| 19 | -post-compile: called after javac compilation
|
|---|
| 20 | -pre-compile-single: called before javac compilation of single file
|
|---|
| 21 | -post-compile-single: called after javac compilation of single file
|
|---|
| 22 | -pre-compile-test: called before javac compilation of JUnit tests
|
|---|
| 23 | -post-compile-test: called after javac compilation of JUnit tests
|
|---|
| 24 | -pre-compile-test-single: called before javac compilation of single JUnit test
|
|---|
| 25 | -post-compile-test-single: called after javac compilation of single JUunit test
|
|---|
| 26 | -pre-jar: called before JAR building
|
|---|
| 27 | -post-jar: called after JAR building
|
|---|
| 28 | -post-clean: called after cleaning build products
|
|---|
| 29 |
|
|---|
| 30 | (Targets beginning with '-' are not intended to be called on their own.)
|
|---|
| 31 |
|
|---|
| 32 | Example of inserting an obfuscator after compilation could look like this:
|
|---|
| 33 |
|
|---|
| 34 | <target name="-post-compile">
|
|---|
| 35 | <obfuscate>
|
|---|
| 36 | <fileset dir="${build.classes.dir}"/>
|
|---|
| 37 | </obfuscate>
|
|---|
| 38 | </target>
|
|---|
| 39 |
|
|---|
| 40 | For list of available properties check the imported
|
|---|
| 41 | nbproject/build-impl.xml file.
|
|---|
| 42 |
|
|---|
| 43 |
|
|---|
| 44 | Another way to customize the build is by overriding existing main targets.
|
|---|
| 45 | The targets of interest are:
|
|---|
| 46 |
|
|---|
| 47 | -init-macrodef-javac: defines macro for javac compilation
|
|---|
| 48 | -init-macrodef-junit: defines macro for junit execution
|
|---|
| 49 | -init-macrodef-debug: defines macro for class debugging
|
|---|
| 50 | -init-macrodef-java: defines macro for class execution
|
|---|
| 51 | -do-jar-with-manifest: JAR building (if you are using a manifest)
|
|---|
| 52 | -do-jar-without-manifest: JAR building (if you are not using a manifest)
|
|---|
| 53 | run: execution of project
|
|---|
| 54 | -javadoc-build: Javadoc generation
|
|---|
| 55 | test-report: JUnit report generation
|
|---|
| 56 |
|
|---|
| 57 | An example of overriding the target for project execution could look like this:
|
|---|
| 58 |
|
|---|
| 59 | <target name="run" depends="RouteGUI-impl.jar">
|
|---|
| 60 | <exec dir="bin" executable="launcher.exe">
|
|---|
| 61 | <arg file="${dist.jar}"/>
|
|---|
| 62 | </exec>
|
|---|
| 63 | </target>
|
|---|
| 64 |
|
|---|
| 65 | Notice that the overridden target depends on the jar target and not only on
|
|---|
| 66 | the compile target as the regular run target does. Again, for a list of available
|
|---|
| 67 | properties which you can use, check the target you are overriding in the
|
|---|
| 68 | nbproject/build-impl.xml file.
|
|---|
| 69 |
|
|---|
| 70 | -->
|
|---|
| 71 | </project>
|
|---|
