commit | author | age
|
2e729d
|
1 |
<?xml version="1.0" encoding="UTF-8"?> |
JK |
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="Brydz" default="jar" basedir="."> |
|
6 |
<description>Builds, tests, and runs the project .</description> |
|
7 |
<import file="nbproject/build-impl.xml"/> |
|
8 |
<!-- |
|
9 |
|
|
10 |
There exist several targets which are by default empty and which can be |
|
11 |
used for execution of your tasks. These targets are usually executed |
|
12 |
before and after some main targets. They are: |
|
13 |
|
|
14 |
pre-init: called before initialization of project properties |
|
15 |
post-init: called after initialization of project properties |
|
16 |
pre-preprocess: called before text preprocessing of sources |
|
17 |
post-preprocess: called after text preprocessing of sources |
|
18 |
pre-compile: called before source compilation |
|
19 |
post-compile: called after source compilation |
|
20 |
pre-obfuscate: called before obfuscation |
|
21 |
post-obfuscate: called after obfuscation |
|
22 |
pre-preverify: called before preverification |
|
23 |
post-preverify: called after preverification |
|
24 |
pre-jar: called before jar building |
|
25 |
post-jar: called after jar building |
|
26 |
pre-build: called before final distribution building |
|
27 |
post-build: called after final distribution building |
|
28 |
pre-clean: called before cleaning build products |
|
29 |
post-clean: called after cleaning build products |
|
30 |
|
|
31 |
Example of pluging a my-special-task after the compilation could look like |
|
32 |
|
|
33 |
<target name="post-compile"> |
|
34 |
<my-special-task> |
|
35 |
<fileset dir="${build.classes.dir}"/> |
|
36 |
</my-special-task> |
|
37 |
</target> |
|
38 |
|
|
39 |
For list of available properties check the imported |
|
40 |
nbproject/build-impl.xml file. |
|
41 |
|
|
42 |
Other way how to customize the build is by overriding existing main targets. |
|
43 |
The target of interest are: |
|
44 |
|
|
45 |
preprocess: preprocessing |
|
46 |
extract-libs: extraction of libraries and resources |
|
47 |
compile: compilation |
|
48 |
create-jad: construction of jad and jar manifest source |
|
49 |
obfuscate: obfuscation |
|
50 |
preverify: preverification |
|
51 |
jar: jar archive building |
|
52 |
run: execution |
|
53 |
debug: execution in debug mode |
|
54 |
build: building of the final distribution |
|
55 |
javadoc: javadoc generation |
|
56 |
|
|
57 |
Example of overriding the target for project execution could look like |
|
58 |
|
|
59 |
<target name="run" depends="init,jar"> |
|
60 |
<my-special-exec jadfile="${dist.dir}/${dist.jad}"/> |
|
61 |
</target> |
|
62 |
|
|
63 |
Be careful about correct dependencies when overriding original target. |
|
64 |
Again, for list of available properties which you can use check the target |
|
65 |
you are overriding in nbproject/build-impl.xml file. |
|
66 |
|
|
67 |
A special target for-all-configs can be used to run some specific targets for |
|
68 |
all project configurations in a sequence. File nbproject/build-impl.xml |
|
69 |
already contains some "for-all" targets: |
|
70 |
|
|
71 |
jar-all |
|
72 |
javadoc-all |
|
73 |
clean-all |
|
74 |
|
|
75 |
Example of definition of target iterating over all project configurations: |
|
76 |
|
|
77 |
<target name="jar-all"> |
|
78 |
<property name="target.to.call" value="jar"/> |
|
79 |
<antcall target="for-all-configs"/> |
|
80 |
</target> |
|
81 |
|
|
82 |
--> |
|
83 |
</project> |