1 <!-- |
|
2 # |
|
3 # Copyright (c) 2008-2009 Nokia Corporation and/or its subsidiary(-ies). |
|
4 # All rights reserved. |
|
5 # This component and the accompanying materials are made available |
|
6 # under the terms of "Eclipse Public License v1.0" |
|
7 # which accompanies this distribution, and is available |
|
8 # at the URL "http://www.eclipse.org/legal/epl-v10.html". |
|
9 # |
|
10 # Initial Contributors: |
|
11 # Nokia Corporation - initial contribution. |
|
12 # |
|
13 # Contributors: |
|
14 # |
|
15 # Description: |
|
16 # |
|
17 --> |
|
18 |
|
19 <?xml version="1.0" encoding="UTF-8"?> |
|
20 <!-- You may freely edit this file. See commented blocks below for --> |
|
21 <!-- some examples of how to customize the build. --> |
|
22 <!-- (If you delete it and reopen the project it will be recreated.) --> |
|
23 <project name="MobInfoProp" default="jar" basedir="."> |
|
24 <description>Builds, tests, and runs the project .</description> |
|
25 <import file="nbproject/buildimpl.xml"/> |
|
26 <!-- |
|
27 |
|
28 There exist several targets which are by default empty and which can be |
|
29 used for execution of your tasks. These targets are usually executed |
|
30 before and after some main targets. They are: |
|
31 |
|
32 pre-init: called before initialization of project properties |
|
33 post-init: called after initialization of project properties |
|
34 pre-preprocess: called before text preprocessing of sources |
|
35 post-preprocess: called after text preprocessing of sources |
|
36 pre-compile: called before source compilation |
|
37 post-compile: called after source compilation |
|
38 pre-obfuscate: called before obfuscation |
|
39 post-obfuscate: called after obfuscation |
|
40 pre-preverify: called before preverification |
|
41 post-preverify: called after preverification |
|
42 pre-jar: called before jar building |
|
43 post-jar: called after jar building |
|
44 pre-build: called before final distribution building |
|
45 post-build: called after final distribution building |
|
46 pre-clean: called before cleaning build products |
|
47 post-clean: called after cleaning build products |
|
48 |
|
49 Example of pluging a my-special-task after the compilation could look like |
|
50 |
|
51 <target name="post-compile"> |
|
52 <my-special-task> |
|
53 <fileset dir="${build.classes.dir}"/> |
|
54 </my-special-task> |
|
55 </target> |
|
56 |
|
57 For list of available properties check the imported |
|
58 nbproject/buildimpl.xml file. |
|
59 |
|
60 Other way how to customize the build is by overriding existing main targets. |
|
61 The target of interest are: |
|
62 |
|
63 preprocess: preprocessing |
|
64 extract-libs: extraction of libraries and resources |
|
65 compile: compilation |
|
66 create-jad: construction of jad and jar manifest source |
|
67 obfuscate: obfuscation |
|
68 preverify: preverification |
|
69 jar: jar archive building |
|
70 run: execution |
|
71 debug: execution in debug mode |
|
72 build: building of the final distribution |
|
73 javadoc: javadoc generation |
|
74 |
|
75 Example of overriding the target for project execution could look like |
|
76 |
|
77 <target name="run" depends="init,jar"> |
|
78 <my-special-exec jadfile="${dist.dir}/${dist.jad}"/> |
|
79 </target> |
|
80 |
|
81 Be careful about correct dependencies when overriding original target. |
|
82 Again, for list of available properties which you can use check the target |
|
83 you are overriding in nbproject/buildimpl.xml file. |
|
84 |
|
85 A special target for-all-configs can be used to run some specific targets for |
|
86 all project configurations in a sequence. File nbproject/buildimpl.xml |
|
87 already contains some "for-all" targets: |
|
88 |
|
89 jar-all |
|
90 javadoc-all |
|
91 clean-all |
|
92 |
|
93 Example of definition of target iterating over all project configurations: |
|
94 |
|
95 <target name="jar-all"> |
|
96 <property name="target.to.call" value="jar"/> |
|
97 <antcall target="for-all-configs"/> |
|
98 </target> |
|
99 |
|
100 --> |
|
101 </project> |
|