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