forked from undera/jmeter-plugins
-
Notifications
You must be signed in to change notification settings - Fork 0
/
build.xml
132 lines (110 loc) · 5.75 KB
/
build.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
<?xml version="1.0" encoding="UTF-8"?>
<project name="JMeterPlugins" default="default" basedir=".">
<description>Contains specific for JMeterPlugins build steps, all other steps are managed by NetBeans.</description>
<!-- We rely on NetBeans build instructions file -->
<!-- For build instructions please visit http://code.google.com/p/jmeter-plugins/wiki/BuildingFromSource -->
<import file="nbproject/build-impl.xml"/>
<!--
There exist several targets which are by default empty and which can be
used for execution of your tasks. These targets are usually executed
before and after some main targets. They are:
-pre-init: called before initialization of project properties
-post-init: called after initialization of project properties
-pre-compile: called before javac compilation
-post-compile: called after javac compilation
-pre-compile-single: called before javac compilation of single file
-post-compile-single: called after javac compilation of single file
-pre-compile-test: called before javac compilation of JUnit tests
-post-compile-test: called after javac compilation of JUnit tests
-pre-compile-test-single: called before javac compilation of single JUnit test
-post-compile-test-single: called after javac compilation of single JUunit test
-pre-jar: called before JAR building
-post-jar: called after JAR building
-post-clean: called after cleaning build products
(Targets beginning with '-' are not intended to be called on their own.)
Example of inserting an obfuscator after compilation could look like this:
<target name="-post-compile">
<obfuscate>
<fileset dir="${build.classes.dir}"/>
</obfuscate>
</target>
For list of available properties check the imported
nbproject/build-impl.xml file.
Another way to customize the build is by overriding existing main targets.
The targets of interest are:
-init-macrodef-javac: defines macro for javac compilation
-init-macrodef-junit: defines macro for junit execution
-init-macrodef-debug: defines macro for class debugging
-init-macrodef-java: defines macro for class execution
-do-jar-with-manifest: JAR building (if you are using a manifest)
-do-jar-without-manifest: JAR building (if you are not using a manifest)
run: execution of project
-javadoc-build: Javadoc generation
test-report: JUnit report generation
An example of overriding the target for project execution could look like this:
<target name="run" depends="JMeterPlugins-impl.jar">
<exec dir="bin" executable="launcher.exe">
<arg file="${dist.jar}"/>
</exec>
</target>
Notice that the overridden target depends on the jar target and not only on
the compile target as the regular run target does. Again, for a list of available
properties which you can use, check the target you are overriding in the
nbproject/build-impl.xml file.
-->
<target name="update-jar" if="${agent.built}">
<jar file="${dist.jar}" update="yes"
basedir="../agent/build/classes" includes="kg/apc/perfmon/client*">
</jar>
<jar file="${dist.jar}" update="yes"
basedir="../agent/build/classes" includes="kg/apc/perfmon/client/*">
</jar>
<jar file="${dist.jar}" update="yes"
basedir="../agent/build/classes" includes="kg/apc/perfmon/metrics*">
</jar>
<jar file="${dist.jar}" update="yes"
basedir="../agent/build/classes" includes="kg/apc/perfmon/metrics/*">
</jar>
<jar file="${dist.jar}" update="yes"
basedir="../agent/build/classes" includes="kg/apc/jmeter/perfmon/agent*">
</jar>
<jar file="${dist.jar}" update="yes"
basedir="../agent/build/classes" includes="kg/apc/jmeter/perfmon/agent/*">
</jar>
</target>
<!-- APC: I see no problems in making package always. It is quick enough now. -->
<target name="-post-jar">
<!-- Stef was right and we'll pack agent client into jar -->
<condition property="agent.built">
<available file="../agent/build/classes" />
</condition>
<antcall target="update-jar">
<param name="agent.built" value="${agent.built}" />
</antcall>
<!-- APC: for easy debugging environment we copy JAR
to jmeter/lib/ext, defined by property jmeter.lib.ext
in private.properties file -->
<fail message="jmeter.lib.ext not available">
<condition>
<not>
<available file="${jmeter.lib.ext}" />
</not>
</condition>
</fail>
<copy tofile="${dist.dir}/JMeterPlugins.jar" file="${dist.jar}" verbose="true" />
<!-- If you failed here, consider setting in project.properties
dist.jar=${dist.dir}/JMeterPlugins.jar -->
<fail message="File not found: ${dist.dir}/JMeterPlugins.jar">
<condition>
<not>
<available file="${dist.dir}/JMeterPlugins.jar" />
</not>
</condition>
</fail>
<copy todir="${jmeter.lib.ext}" file="${dist.jar}" verbose="true" />
<!-- SH: handle plugin nameupdater.properties -->
<zip destfile="${dist.jar}" update="yes">
<zipfileset dir="." includes="org.apache.jmeter.nameupdater.properties" prefix="META-INF/resources"/>
</zip>
</target>
</project>