|
0
|
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="SSDT_Ant_Tasks" default="default" basedir=".">
|
|
|
11 <description>Builds, tests, and runs the project SSDT Ant Tasks.</description>
|
|
|
12 <import file="nbproject/build-impl.xml"/>
|
|
|
13 <!--
|
|
|
14
|
|
|
15 There exist several targets which are by default empty and which can be
|
|
|
16 used for execution of your tasks. These targets are usually executed
|
|
|
17 before and after some main targets. They are:
|
|
|
18
|
|
|
19 -pre-init: called before initialization of project properties
|
|
|
20 -post-init: called after initialization of project properties
|
|
|
21 -pre-compile: called before javac compilation
|
|
|
22 -post-compile: called after javac compilation
|
|
|
23 -pre-compile-single: called before javac compilation of single file
|
|
|
24 -post-compile-single: called after javac compilation of single file
|
|
|
25 -pre-compile-test: called before javac compilation of JUnit tests
|
|
|
26 -post-compile-test: called after javac compilation of JUnit tests
|
|
|
27 -pre-compile-test-single: called before javac compilation of single JUnit test
|
|
|
28 -post-compile-test-single: called after javac compilation of single JUunit test
|
|
|
29 -pre-jar: called before JAR building
|
|
|
30 -post-jar: called after JAR building
|
|
|
31 -post-clean: called after cleaning build products
|
|
|
32
|
|
|
33 (Targets beginning with '-' are not intended to be called on their own.)
|
|
|
34
|
|
|
35 Example of inserting an obfuscator after compilation could look like this:
|
|
|
36
|
|
|
37 <target name="-post-compile">
|
|
|
38 <obfuscate>
|
|
|
39 <fileset dir="${build.classes.dir}"/>
|
|
|
40 </obfuscate>
|
|
|
41 </target>
|
|
|
42
|
|
|
43 For list of available properties check the imported
|
|
|
44 nbproject/build-impl.xml file.
|
|
|
45
|
|
|
46
|
|
|
47 Another way to customize the build is by overriding existing main targets.
|
|
|
48 The targets of interest are:
|
|
|
49
|
|
|
50 -init-macrodef-javac: defines macro for javac compilation
|
|
|
51 -init-macrodef-junit: defines macro for junit execution
|
|
|
52 -init-macrodef-debug: defines macro for class debugging
|
|
|
53 -init-macrodef-java: defines macro for class execution
|
|
|
54 -do-jar-with-manifest: JAR building (if you are using a manifest)
|
|
|
55 -do-jar-without-manifest: JAR building (if you are not using a manifest)
|
|
|
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="SSDT_Ant_Tasks-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>
|
