forked from sebasjm/antlr
-
Notifications
You must be signed in to change notification settings - Fork 0
/
pom.xml
311 lines (266 loc) · 11.7 KB
/
pom.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
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
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<!--
The ANTLR Maven artifacts are now released via the Sonotype OSS
repository, which means that they are synced to Maven central
within a few minutes of hitting the release repo for Sonotype.
To enable this, we inherit from the Sonotype provided parent
pom. However, we must also configure our .m2/settings.xml to include
the snapshot and staging server and the sonotype password. This
means that only ANTLR developers can released the artifacts, but
anyone can build locally.
-->
<parent>
<groupId>org.sonatype.oss</groupId>
<artifactId>oss-parent</artifactId>
<version>7</version>
</parent>
<modelVersion>4.0.0</modelVersion>
<groupId>org.antlr</groupId>
<artifactId>antlr-master</artifactId>
<packaging>pom</packaging>
<version>3.4</version>
<name>ANTLR Master build control POM 3.4</name>
<url>http://maven.apache.org</url>
<!--
What version of ANTLR are we building? This sets the
the version number for all other things that are built
as part of an ANTLR release, unless they override or
ignore it. We do this via a properites file for this
pom.
-->
<!--
This is the master pom for building the ANTLR
toolset and runtime (Java) at the specific level
defined above. Hence we specify here the modules that
this pom will build when we build this pom in certain profiles.
-->
<!--
Make sure that the build is not platform dependent (I.E show that
all the files in the source tree are in UTF-8 format.
-->
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>
<profiles>
<profile>
<id>standard</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<modules>
<module>runtime/Java</module>
<module>tool</module>
<module>antlr3-maven-plugin</module>
<module>gunit</module>
<module>gunit-maven-plugin</module>
<module>antlr3-maven-archetype</module>
</modules>
</profile>
<!--
Activate this profile to build ONLY the Uber jar, which is the
ANTLR tool and its dependencies (no plugins etc).
mvn -Duber -DskipTests package assembly:assembly
-->
<profile>
<id>uber</id>
<activation>
<property>
<name>uber</name>
<value>true</value>
</property>
</activation>
<modules>
<module>runtime/Java</module>
<module>tool</module>
</modules>
<build>
<plugins>
<plugin>
<!--
Build an uber-jar for the ANTLR Tool that is packaged with all the other dependencies,
such as the antlr-runtime and stringtemplate etc. This will be useful
for developers, who then do not need to download anything else or
remember that they need stringtemplate.jar in their CLASSPATH and so
on.
This does not preclude any of the module generated jars from
being used on their own of course.
Here, we also build a master source jar as I was unable to pursuade
this plugin to use multiple configurations and not have the thing
screw up because of multiple modules :-(
-->
<artifactId>maven-assembly-plugin</artifactId>
<version>2.2.1</version>
<!--
Do not make the child modules build an assembly
-->
<inherited>false</inherited>
<configuration>
<descriptors>
<descriptor>antlrjar.xml</descriptor>
<descriptor>antlrsources.xml</descriptor>
</descriptors>
<!--
Specify that we want the resulting jar to be executable
via java -jar, which we do by modifying the manifest
of course.
-->
<archive>
<manifest>
<mainClass>org.antlr.Tool</mainClass>
</manifest>
</archive>
</configuration>
</plugin>
</plugins>
</build>
</profile>
<profile>
<id>release-sign-artifacts</id>
<activation>
<property>
<name>deploy</name>
<value>true</value>
</property>
</activation>
<modules>
<module>runtime/Java</module>
<module>tool</module>
<module>antlr3-maven-plugin</module>
<module>gunit</module>
<module>gunit-maven-plugin</module>
<module>antlr3-maven-archetype</module>
</modules>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-gpg-plugin</artifactId>
<version>1.3</version>
<executions>
<execution>
<id>sign-artifacts</id>
<phase>verify</phase>
<goals>
<goal>sign</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>2.8</version>
<executions>
<execution>
<id>attach-javadocs</id>
<goals>
<goal>jar</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<version>2.1.2</version>
<executions>
<execution>
<id>attach-sources</id>
<goals>
<goal>jar</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
</profiles>
<!--
Tell Maven which other artifacts we need in order to
build, run and test the ANTLR jars.
This is the master pom, and so it only contains those
dependencies that are common to all the modules below
or are just included for test
-->
<dependencyManagement>
<dependencies>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.8.2</version>
<scope>test</scope>
</dependency>
</dependencies>
</dependencyManagement>
<build>
<defaultGoal>install</defaultGoal>
<!--
The following filter definition means that both the master
project and the sub projects will read in a file in the same
directory as the pom.xml is located and set any properties
that are defined there in the standard x=y format. These
properties can then be referenced via ${x} in any resource
file specified in any pom. So, there is a master antlr.config
file in the same location as this pom.xml file and here you can
define anything that is relevant to all the modules that we
build here. However each module also has an antlr.config file
where you can override property values from the master file or
define things that are only relevant to that module.
-->
<filters>
<filter>antlr.config</filter>
</filters>
<resources>
<resource>
<directory>src/main/resources</directory>
<filtering>true</filtering>
</resource>
</resources>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>buildnumber-maven-plugin</artifactId>
<version>1.0-beta-2</version>
<configuration>
<format>{0,date,MMM dd, yyyy} {0,time,kk:mm:ss}</format>
<items>
<item>timestamp</item>
</items>
</configuration>
<executions>
<execution>
<phase>validate</phase>
<goals>
<goal>create</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.3.2</version>
<configuration>
<source>1.6</source>
<target>jsr14</target>
<sourceDirectory>src</sourceDirectory>
</configuration>
</plugin>
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.9</version>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>findbugs-maven-plugin</artifactId>
<version>2.3.2</version>
<configuration>
<findbugsXmlOutput>true</findbugsXmlOutput>
<findbugsXmlWithMessages>true</findbugsXmlWithMessages>
<xmlOutput>true</xmlOutput>
</configuration>
</plugin>
</plugins>
</build>
</project>