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