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
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
|
<?xml version="1.0" encoding="ISO-8859-1"?>
<document>
<head>
<name>CoveragePostCompiler: GroboCoverage Ant Tasks</name>
<doc-version>$Date: 2004/04/06 02:57:09 $</doc-version>
<author>Matt Albrecht</author>
</head>
<body>
<P>
<link name="v2_antdoc">All Tasks</link>
</P>
<anttask name="coveragepostcompiler">
<description>
<i>Deprecated - use
<link name="v2_antdoc_grobo-instrument">grobo-instrument</link>
instead.</i>
<p>
Recompiles the provided class files to a separate directory, and stores
the compilation generated data (for use in report generation) to another
directory.
</p>
</description>
<ant-nested-element name="fileset">
<description>
the <ant-link href="using.html#fileset">FileSet</ant-link> to use for
defining all the class files to recompile. Note that no matter what
is specified in the file sets, only files ending in ".class"
(case-insensitive) will be recompiled. There may be multiple of these
file sets specified.
</description>
</ant-nested-element>
<ant-nested-element name="analysismodule">
<description>
Defines a single analysis module to use in the analysis of each
class file that is recompiled. An analysis module creates coverage
details for the class specific to its measure, such as line-count or
branch count. Multiple of these modules may be specified. Each
analysis module will have its own report generated.
</description>
<ant-nested-element name="classpath">
<description>
Analysismodule's <i>classpath</i> attribute is a
<ant-link href="using.html#path">PATH like structure</ant-link>
and can also be set via a nested classpath element.
</description>
</ant-nested-element>
<ant-parameter>
<attribute>name</attribute>
<description>the name of the analysis module to load. The only
current acceptable values are:
<UL>
<definition term="linecount">
counts the source code line coverage. This requires the
line information to be stored in the class file.
</definition>
<definition term="bytecode">
counts the coverage of the class file's bytecode. This
is the most detailed look at exactly what amount of code
is and is not being covered, but can be hard to read.
</definition>
<definition term="branch">
counts the coverage of each branch by looking at the
bytecode branching instructions.
</definition>
<definition term="call-pair">
counts the coverage of each method invocation.
</definition>
<definition term="function">
counts the "function" or "method" entry coverage; when
the execution enters a method, that method is marked as
covered.
</definition>
</UL>
</description>
<required>One of <code>name</code> (alternatively,
<code>type</code>) or <code>classname</code> must be
specified</required>
</ant-parameter>
<ant-parameter>
<attribute>type</attribute>
<description>an alternative to the <code>name</code> attribute.
</description>
<required>One of <code>name</code> (alternatively,
<code>type</code>) or <code>classname</code> must be
specified</required>
</ant-parameter>
<ant-parameter>
<attribute>classname</attribute>
<description>Loads a non-standard analysis module, using this
parameter as a the fully-qualified class name of the analysis
module class. If this is specified, then it will use the
classpathref parameter, embedded classpath element, or loaderref
parameter to reference the classpath from which to load the
module, if any are provided. If none are provided, then
the classloader for the task will be used instead.
</description>
<required>One of <code>name</code> (alternatively,
<code>type</code>) or <code>classname</code> must be
specified</required>
</ant-parameter>
<ant-parameter>
<attribute>classpathref</attribute>
<description>Reference to a classpath to use when looking up
<code>classname</code>.
</description>
<required>No</required>
</ant-parameter>
<ant-parameter>
<attribute>loaderRef</attribute>
<description>the name of the loader that is used to load the
class, constructed from the specified classpath.
Use this to allow multiple tasks/types to be loaded with the
same loader, so they can call each other.
</description>
<required>No</required>
</ant-parameter>
</ant-nested-element>
<ant-nested-element name="logsettings">
<description>
Sets up how the logs are generated by the covered classes.
This allows for configuration of the
<code>grobocoverage.properties</code> file (which tells the
coverage-enabled classes everything they need
during operation to run correctly), and generates that properties
file for you.
</description>
<ant-parameter>
<attribute>factory</attribute>
<description>the factory class to handle the logging. If no
package is specified, then this property will prepend
"net.sourceforge.groboutils.codecoverage.v2.logger." to the
given factory name. Currently, there are two types of loggers:
<ol>
<definition term="DirectoryChannelLoggerFactory">(default)
This is the safest logger, but the slowest. On each
logging request, it opens the log file, writes the log
element, then closes the log file, all in a VM-wide
synchronized block. Using this logger, you will likely
see a large amount of disk access. The <code>logDir</code>
parameter (below) defines the directory to place all
the channel log data (default directory is
"./.cover-logs").</definition>
<definition term="CacheDirChannelLoggerFactory">
This is a faster logger. It keeps a sized cache of open
log files in memory, each log file being a buffered
file. This has a danger of possibly not closing or flushing
its open log files on VM shutdown. If the VM is JDK 1.3
compatible, the logger will add a shutdown hook to
attempt to close its opened files. Using this logger,
you should see large disk access when the VM ends.
It uses the <code>logDir</code> parameter (below) that
the <code>DirectoryChannelLoggerFactory</code> uses,
and also uses the <code>cachesize</code> parameter,
which defines the maximum number of opened files
stored in the cache per channel (default size is 25,
but you should match this to the limitations of the
operating system).
<p>
There's a pending issue with this logger (<a
href="https://sourceforge.net/tracker/index.php?func=detail&aid=902884&group_id=22594&atid=375589"
>bug 902884</a>).
</p>
</definition>
<definition term="MinDirChannelLoggerFactory">
This operates identically to
<code>DirectoryChannelLoggerFactory</code>,
but caches the encountered covered items, and only
writes new elements to the log files. This is
JDK 1.2 dependent, and may eat up lots of memory. However,
for those that are encountering issues due to enormous
log files, moving to this logger should fix the problem.
Also, this should reduce file I/O.
</definition>
</ol>
</description>
<required>No</required>
</ant-parameter>
<ant-parameter>
<attribute>logDir</attribute>
<description>the directory that all the coverage logging
data will be put. Must match the report task's
<code>logDir</code> parameter.
</description>
<required>No</required>
</ant-parameter>
<ant-parameter>
<attribute>cachesize</attribute>
<description>the number of concurrent files to keep open.
Only used by the <code>CacheDirChannelLoggerFactory</code>.
</description>
<required>No</required>
</ant-parameter>
</ant-nested-element>
<ant-parameter>
<attribute>datadir</attribute>
<description>the name of the directory to send the analysis module
generated data to. This same directory should be specified in the
<tt>coveragereport</tt> task's <tt>datadir</tt> attribute as well.
</description>
<required>Yes</required>
</ant-parameter>
<ant-parameter>
<attribute>outclassdir</attribute>
<description>The name of the directory in which the recompiled class
files are saved. This directory should <em>never</em> be confused with
the original classes: these classes are slower and "fatter" than the
originals.
</description>
<required>Yes</required>
</ant-parameter>
<ant-example>
<source>
<coveragepostcompiler
outclassdir="coverage/classes"
datadir="coverage/data"
>
<analysismodule name="linecount" />
<fileset dir="${dirs.classes}" />
<fileset dir="${dirs.classes2}">
<excludes name="dont/cover/these/*.class" />
</fileset>
<logsettings logdir="coverage/logs" />
</coveragepostcompiler>
</source>
<description>
Recompiles all the classes located in <tt>${dirs.classes}</tt> using
the linecount analysis module, and recompiles all the classes from
<code>${dirs.classes2}</code> except those in the
<code>dont.cover.these</code> package. All the recompiled classes are
stored in <tt>coverage/classes</tt>, and the analysis
module generated data is stored under the
<tt>coverage/data</tt> directory. The default logger factory
(<code>DirectoryChannelLoggerFactory</code>) will be used during runs,
outputting log data to <code>coverage/logs</code>.
</description>
</ant-example>
</anttask>
<P>
<link name="v2_antdoc">All Tasks</link>
</P>
</body>
</document>
|
