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
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
|
<?xml version="1.0" encoding="UTF-8"?>
<!--
This is the assembly descriptor for building a full source code
distribution of ANTLR and all its related components. This assmebly
only includes the Java oriented source code, hence only the Java runtime
is included in the resulting jar.
The resulting jar is distribution that can be expanded with:
jar xvf antlr-master-3.x.x-src.jar
The output directory will be antlr-master-3.x.x and in here will be
the BUILD.txt fie, which explains how to build ANTLR.
Jim Idle - May, 2009
-->
<assembly>
<!-- The name of this assembly descriptor, which is referenced in
the master pom.xml using <assemblyRef> (although in fact we
reference the file name that contains it to avoid cluttering
the pom.
-->
<id>src</id>
<!-- We have elected to produce only a jar output and to use the line
endings of whatever platform we are running on. More formats
can be added for simultaneous production, such as <format>zip</format>
-->
<formats>
<format>jar</format>
</formats>
<!--
The resulting archives will hve a base directory named after the master
artifact, rather than just extract into the current directory.
-->
<includeBaseDirectory>true</includeBaseDirectory>
<!-- We need to described the source code of each of the modules we want
including in the archive. In the main this is because we did not store
the modules in perforce using directory names that match the module
names. This was for historic reasons as we already moved everything
about massively, jsut to move to Maven inthe first place.
-->
<moduleSets>
<!-- Describe the gUnit source code.
-->
<moduleSet>
<!-- The Maven artifact name tells the assembly artifact a bunch
of information to start with, such as its location in the current
tree and so on.
-->
<includes>
<include>org.antlr:gunit</include>
</includes>
<!-- What sources do we wish to include from this module?
-->
<sources>
<fileSets>
<!-- We have one file set, being the src sub-directory, which in
the output archive, we also want to be called src/
-->
<fileSet>
<directory>src</directory>
<outputDirectory>src</outputDirectory>
</fileSet>
<!-- In the base gUnit directory, we need to include a number
of files that either document the module or control the
build. These are not underneath the src directory of course
so they need to be named here (which nicely documents what
is included.
-->
<fileSet>
<includes>
<include>pom.xml</include>
<include>CHANGES.txt</include>
<include>LICENSE.txt</include>
<include>README.txt</include>
<include>antlr.config</include>
</includes>
</fileSet>
</fileSets>
</sources>
</moduleSet>
<!-- Describe the gUnit source code.
-->
<moduleSet>
<!-- The Maven artifact name tells the assembly artifact a bunch
of information to start with, such as its location in the current
tree and so on.
-->
<includes>
<include>org.antlr:antlr-runtime</include>
</includes>
<!-- What sources do we wish to include from this module?
-->
<sources>
<!-- Because the Java runtime source is not in a directory
called antlr-runtime, directly underneath the master
directory, we need to map the output directory so that
instead of starting with the name of the artifact, it
is in the place where the build expects it.
-->
<outputDirectoryMapping>runtime/Java</outputDirectoryMapping>
<fileSets>
<!-- We have one file set, being the src sub-directory, which in
the output archive, we also want to be called src/
-->
<fileSet>
<directory>src</directory>
<outputDirectory>src</outputDirectory>
</fileSet>
<!-- In the base runtime/Java directory, we need to include a number
of files that either document the module or control the
build. These are not underneath the src directory of course
so they need to be named here (which nicely documents what
is included.
-->
<fileSet>
<includes>
<include>pom.xml</include>
<include>doxyfile</include>
<include>antlr.config</include>
</includes>
</fileSet>
</fileSets>
</sources>
</moduleSet>
<!-- Describe the ANTLR tool source code.
-->
<moduleSet>
<includes>
<include>org.antlr:antlr</include>
</includes>
<!-- What sources do we wish to include from this module?
-->
<sources>
<!-- Because the tool source code is not in a directory
called antlr, nor directly underneath the master
directory, we need to map the output directory so that
instead of starting with the name of the artifact, it
is in the place where the build expects it.
-->
<outputDirectoryMapping>tool</outputDirectoryMapping>
<fileSets>
<!-- We have one file set, being the src sub-directory, which in
the output archive, we also want to be called src/
-->
<fileSet>
<directory>src</directory>
<outputDirectory>src</outputDirectory>
</fileSet>
<!-- In the base tool directory, we need to include a number
of files that either document the module or control the
build. These are not underneath the src directory of course
so they need to be named here (which nicely documents what
is included.
-->
<fileSet>
<includes>
<include>pom.xml</include>
<include>CHANGES.txt</include>
<include>LICENSE.txt</include>
<include>README.txt</include>
<include>antlr.config</include>
</includes>
</fileSet>
</fileSets>
</sources>
</moduleSet>
<!-- Describe the ANTLR maven plugin source code.
Strictly speaking, this is not a sub module of the tool because it
relies on the tool, runtime, and gunit modules. However, it is natural
part of the Java source set and so I found a way to build it as a sub-module
and include it in the source set.
-->
<moduleSet>
<includes>
<include>org.antlr:antlr3-maven-plugin</include>
</includes>
<!-- What sources do we wish to include from this module?
-->
<sources>
<fileSets>
<!-- We have one file set, being the src sub-directory, which in
the output archive, we also want to be called src/
-->
<fileSet>
<directory>src</directory>
<outputDirectory>src</outputDirectory>
</fileSet>
<!-- In the base plugin directory, we need to include a number
of files that either document the module or control the
build. These are not underneath the src directory of course
so they need to be named here (which nicely documents what
is included.
-->
<fileSet>
<includes>
<include>pom.xml</include>
</includes>
</fileSet>
</fileSets>
</sources>
</moduleSet>
<!-- Describe the gUnit maven plugin source code.
Strictly speaking, this is not a sub module of the tool because it
relies on the tool, runtime, and gunit modules. However, it is natural
part of the Java source set and so I found a way to build it as a sub-module
and include it in the source set.
-->
<moduleSet>
<includes>
<include>org.antlr:maven-gunit-plugin</include>
</includes>
<!-- What sources do we wish to include from this module?
-->
<sources>
<!-- Because the tool source code is not in a directory
called antlr, nor directly underneath the master
directory, we need to map the output directory so that
instead of starting with the name of the artifact, it
is in the place where the build expects it.
-->
<outputDirectoryMapping>gunit-maven-plugin</outputDirectoryMapping>
<!-- We have one file set, being the src sub-directory, which in
the output archive, we also want to be called src/
-->
<fileSets>
<fileSet>
<directory>src</directory>
<outputDirectory>src</outputDirectory>
</fileSet>
<!-- In the base plugin directory, we need to include a number
of files that either document the module or control the
build. These are not underneath the src directory of course
so they need to be named here (which nicely documents what
is included.
-->
<fileSet>
<includes>
<include>pom.xml</include>
</includes>
</fileSet>
</fileSets>
</sources>
</moduleSet>
</moduleSets>
<!-- In the base directory of the master build directory (the root of all
the other sources), there are a number of files that describe or control
the build (such as the master pom.xml and the BUILD.txt files). Hence
we need to describe them in their own fileset. No output mapping is required here
of course.
-->
<fileSets>
<fileSet>
<includes>
<include>pom.xml</include>
<include>antlrjar.xml</include>
<include>antlrsources.xml</include>
<include>BUILD.txt</include>
</includes>
</fileSet>
</fileSets>
</assembly>
|
