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
319
320
321
322
323
324
325
326
327
|
<?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/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<!-- The AspectJ root POM is the parent, but this module is not a submodule -->
<parent>
<groupId>org.aspectj</groupId>
<artifactId>aspectj-parent</artifactId>
<version>1.9.22-SNAPSHOT</version>
</parent>
<artifactId>lib</artifactId>
<description>
This module downloads + installs libraries used by many tests, especially those running as Ant jobs. You should not
build this module during every build because it is somewhat slow, downloading stuff from 3rd-party websites,
unzipping some libraries (e.g. a full Ant distribution) and creating new ZIP files (e.g. source JARs, compound JARs
containing multiple libraries).
So just run 'mvn compile' once after cloning the AspectJ repository and you should be all set to subsequently build
AspectJ itself. If you forget this step, a Maven Enforcer rule in the AspectJ root POM will fail the build and
remind you to build this module.
Normally you never have to call 'mvn clean' here, but if for some reason the installed libraries are in an
inconsistent state (e.g. after an incomplete download), you can do so and then run 'mvn compile' again.
BTW, running 'mvn compile' multiple times will not repeat any download via Maven Dependency or Download Maven
plugins, but repeat all zip/unzip steps in TrueZIP Maven plugin. So try not to call it unnecessarily.
</description>
<!-- TODO: Add lib (for now, then finally lib) to .gitignore -->
<properties>
<lib.provisioned.marker>provisioned.marker</lib.provisioned.marker>
<lib.ant.name>apache-ant</lib.ant.name>
<lib.ant.artifact>${lib.ant.name}-${lib.ant.version}</lib.ant.artifact>
</properties>
<profiles>
<!-- Profile for provisioning - i.e. downloading and (un)zipping - libraries needed during the build -->
<profile>
<id>provision-libs</id>
<!-- If marker file is missing, activate profile and provision all libraries -->
<activation>
<file>
<missing>${lib.provisioned.marker}</missing>
</file>
</activation>
<build>
<plugins>
<!-- Download libraries + source code which are unavailable in Maven repositories like Maven Central -->
<plugin>
<groupId>com.googlecode.maven-download-plugin</groupId>
<artifactId>download-maven-plugin</artifactId>
<version>1.6.7</version>
<configuration>
<!-- Detect previously failed downloads by verifying checksums of existing files -> retry -->
<alwaysVerifyChecksum>true</alwaysVerifyChecksum>
</configuration>
<executions>
<execution>
<id>download-ant-binaries</id>
<phase>generate-resources</phase>
<goals>
<goal>wget</goal>
</goals>
<configuration>
<url>https://archive.apache.org/dist/ant/binaries/${lib.ant.artifact}-bin.zip</url>
<outputDirectory>ant</outputDirectory>
<sha1>3fa9f816a0c4c63249efad8e6225f2e83794f0c0</sha1>
</configuration>
</execution>
<execution>
<id>download-ant-sources</id>
<phase>generate-resources</phase>
<goals>
<goal>wget</goal>
</goals>
<configuration>
<url>https://archive.apache.org/dist/ant/source/${lib.ant.artifact}-src.zip</url>
<outputDirectory>ant</outputDirectory>
<sha1>b9f3c8c31bb6c9069ad5b655059a17769af12f20</sha1>
</configuration>
</execution>
</executions>
</plugin>
<!-- Download libraries + source code which are available in Maven repositories like Maven Central -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<version>3.1.2</version>
<executions>
<execution>
<id>copy</id>
<phase>generate-resources</phase>
<goals>
<goal>copy</goal>
</goals>
<configuration>
<artifactItems>
<artifactItem>
<groupId>org.aspectj</groupId>
<artifactId>org.eclipse.jdt.core</artifactId>
<version>${jdt.core.version}</version>
<type>jar</type>
<overWrite>false</overWrite>
<outputDirectory>jdtcore-aj</outputDirectory>
<destFileName>jdtcore-for-aspectj.jar</destFileName>
</artifactItem>
<artifactItem>
<groupId>org.aspectj</groupId>
<artifactId>org.eclipse.jdt.core</artifactId>
<version>${jdt.core.version}</version>
<type>java-source</type>
<classifier>sources</classifier>
<overWrite>false</overWrite>
<outputDirectory>jdtcore-aj</outputDirectory>
<destFileName>jdtcore-for-aspectj-src.zip</destFileName>
</artifactItem>
<artifactItem>
<!-- Binary is identical to committed version -->
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<type>jar</type>
<overWrite>false</overWrite>
<outputDirectory>junit</outputDirectory>
<destFileName>junit.jar</destFileName>
</artifactItem>
<artifactItem>
<!-- Binary is identical to committed version -->
<!-- TODO: Is this redundant JUnit JAR in ant/lib really necessary? If so, why? -->
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<type>jar</type>
<overWrite>false</overWrite>
<outputDirectory>ant/lib</outputDirectory>
<destFileName>junit.jar</destFileName>
</artifactItem>
<artifactItem>
<!-- Binary is identical to committed version -->
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<type>jar</type>
<classifier>sources</classifier>
<overWrite>false</overWrite>
<outputDirectory>junit</outputDirectory>
<destFileName>junit-src.zip</destFileName>
</artifactItem>
</artifactItems>
</configuration>
</execution>
</executions>
</plugin>
<!-- (Un)zip downloaded libraries the way our build needs them -->
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>truezip-maven-plugin</artifactId>
<!--
The TrueZIP plugin can seamlessly copy out of or into (nested) ZIP files as if they were normal file system
paths. No additional moves and deletes with Antrun are necessary.
-->
<executions>
<execution>
<id>unzip-ant-binaries</id>
<phase>process-resources</phase>
<goals>
<goal>copy</goal>
</goals>
<configuration>
<verbose>true</verbose>
<fileset>
<directory>ant/${lib.ant.artifact}-bin.zip/${lib.ant.artifact}</directory>
<outputDirectory>ant</outputDirectory>
</fileset>
</configuration>
</execution>
<execution>
<id>zip-ant-sources</id>
<phase>process-resources</phase>
<goals>
<goal>copy</goal>
</goals>
<configuration>
<verbose>true</verbose>
<fileset>
<directory>ant/${lib.ant.artifact}-src.zip/${lib.ant.artifact}/src/main</directory>
<outputDirectory>ant/ant-src.zip</outputDirectory>
</fileset>
</configuration>
</execution>
</executions>
</plugin>
<!--
After all libraries have been provisioned successfully, create a marker file in order to avoid provisioning
them again during the next build
-->
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>build-helper-maven-plugin</artifactId>
<executions>
<execution>
<id>create-marker-file</id>
<phase>process-resources</phase>
<goals>
<goal>bsh-property</goal>
</goals>
<configuration>
<source><![CDATA[
myFile = new File(project.getBasedir(), "${lib.provisioned.marker}");
print("Finished provisioning libraries, creating marker file " + myFile.getCanonicalPath());
myFile.createNewFile();
]]></source>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
<dependencies>
<dependency>
<groupId>org.aspectj</groupId>
<artifactId>org.eclipse.jdt.core</artifactId>
</dependency>
</dependencies>
</profile>
<!-- Profile for including provisioned libraries when running 'mvn clean'; inactive by default, activate manually -->
<profile>
<id>clean-libs</id>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-clean-plugin</artifactId>
<executions>
<execution>
<id>clean-up-libs</id>
<phase>clean</phase>
<goals>
<goal>clean</goal>
</goals>
<configuration>
<filesets>
<fileset>
<directory>.</directory>
<includes>
<include>${lib.provisioned.marker}</include>
<include>ant/**</include>
<include>jdtcore-aj/**</include>
<include>junit/**</include>
</includes>
<followSymlinks>false</followSymlinks>
</fileset>
</filesets>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
</profiles>
<build>
<plugins>
<!--
Heuristic consistency check for existence of provisioned library files. Do not just rely on
${lib.provisioned.marker} file.
-->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-enforcer-plugin</artifactId>
<executions>
<execution>
<id>enforce-libraries-exist</id>
<phase>compile</phase>
<goals>
<goal>enforce</goal>
</goals>
<configuration>
<rules>
<requireFilesExist>
<!--
Do NOT insert any line breaks + indentation inside the message, keep it on a single line.
Maven Enforcer does not strip any whitespace or unindent, which looks quite ugly on the console.
-->
<message>
There is an inconsistency in module subdirectory 'lib'. Please run 'mvn --projects lib -P clean-libs clean compile'. This should take care of cleaning and freshly downloading all necessary libraries to that directory, where some tests expect them to be.
</message>
<files>
<file>${lib.provisioned.marker}</file>
<file>ant/bin/ant.bat</file>
<file>ant/lib/junit.jar</file>
<file>jdtcore-aj/jdtcore-for-aspectj.jar</file>
<file>junit/junit.jar</file>
</files>
</requireFilesExist>
</rules>
<fail>true</fail>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</project>
|