-
Notifications
You must be signed in to change notification settings - Fork 938
Expand file tree
/
Copy pathpom.xml
More file actions
288 lines (264 loc) · 13.1 KB
/
Copy pathpom.xml
File metadata and controls
288 lines (264 loc) · 13.1 KB
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
<?xml version="1.0" encoding="UTF-8"?>
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<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 https://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.apache.tika</groupId>
<artifactId>tika-parent</artifactId>
<version>${revision}</version>
<relativePath>tika-parent/pom.xml</relativePath>
</parent>
<artifactId>tika</artifactId>
<packaging>pom</packaging>
<name>Apache Tika</name>
<url>https://tika.apache.org</url>
<modules>
<module>tika-parent</module>
<module>tika-bom</module>
<module>tika-core</module>
<module>tika-annotation-processor</module>
<module>tika-serialization</module>
<module>tika-plugins-core</module>
<module>tika-detectors</module>
<module>tika-ml</module>
<module>tika-encoding-detectors</module>
<module>tika-parsers</module>
<module>tika-bundles</module>
<module>tika-xmp</module>
<module>tika-langdetect</module>
<module>tika-pipes</module>
<module>tika-grpc</module>
<module>tika-app</module>
<module>tika-server</module>
<module>tika-integration-tests</module>
<module>tika-eval</module>
<module>tika-translate</module>
<module>tika-example</module>
<module>tika-java7</module>
<module>tika-handlers</module>
</modules>
<profiles>
<profile>
<id>e2e</id>
<modules>
<module>tika-e2e-tests</module>
</modules>
</profile>
<profile>
<id>apache-release</id>
<modules>
<module>docs</module>
</modules>
<properties>
<username>${user.name}</username>
</properties>
<build>
<plugins>
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<executions>
<execution>
<id>src</id>
<goals>
<goal>single</goal>
</goals>
<phase>package</phase>
<configuration>
<descriptors>
<descriptor>assembly.xml</descriptor>
</descriptors>
</configuration>
</execution>
<execution>
<id>source-release-assembly</id>
<configuration>
<skipAssembly>true</skipAssembly>
</configuration>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<version>${maven.antrun.version}</version>
<executions>
<execution>
<goals>
<goal>run</goal>
</goals>
<phase>deploy</phase>
<configuration>
<target>
<mkdir dir="${basedir}/target/${project.version}" />
<copy todir="${basedir}/target/${project.version}" flatten="true">
<fileset dir="${basedir}">
<include name="CHANGES.txt" />
<include name="target/*-src.zip*" />
<include name="tika-parsers/tika-parsers-extended/tika-parser-scientific-package/target/tika-parser-scientific-package-${project.version}-shaded.jar*" />
<include name="tika-parsers/tika-parsers-extended/tika-parser-sqlite3-package/target/tika-parser-sqlite3-package-${project.version}-shaded.jar*" />
<include name="tika-parsers/tika-parsers-ml/tika-parser-nlp-package/target/tika-parser-nlp-package-${project.version}-shaded.jar*" />
<include name="tika-app/target/tika-app-${project.version}.zip*" />
<include name="tika-server/tika-server-standard/target/tika-server-standard-${project.version}.zip*" />
<include name="tika-eval/tika-eval-app/target/tika-eval-app-${project.version}.zip*" />
<include name="tika-pipes/tika-pipes-plugins/*/target/tika-pipes-*-${project.version}.zip*" />
</fileset>
</copy>
<!--
TIKA-4733: fail the release build if any expected dist
artifact did not land in target/${project.version}/.
Ant <copy> silently succeeds when an <include> matches
zero files, so a renamed, re-versioned, or forgotten
artifact (or a module whose assembly/shade stopped
producing output) would otherwise yield an incomplete
release candidate with no error. Each <fail> below names
the missing artifact so the gap is obvious. Keep this list
in sync with the <copy> include list above.
-->
<fail message="Release staging missing: CHANGES.txt">
<condition><not><available file="${basedir}/target/${project.version}/CHANGES.txt" /></not></condition>
</fail>
<fail message="Release staging missing: tika-${project.version}-src.zip">
<condition><not><available file="${basedir}/target/${project.version}/tika-${project.version}-src.zip" /></not></condition>
</fail>
<fail message="Release staging missing: tika-parser-scientific-package-${project.version}-shaded.jar">
<condition><not><available file="${basedir}/target/${project.version}/tika-parser-scientific-package-${project.version}-shaded.jar" /></not></condition>
</fail>
<fail message="Release staging missing: tika-parser-sqlite3-package-${project.version}-shaded.jar">
<condition><not><available file="${basedir}/target/${project.version}/tika-parser-sqlite3-package-${project.version}-shaded.jar" /></not></condition>
</fail>
<fail message="Release staging missing: tika-parser-nlp-package-${project.version}-shaded.jar">
<condition><not><available file="${basedir}/target/${project.version}/tika-parser-nlp-package-${project.version}-shaded.jar" /></not></condition>
</fail>
<fail message="Release staging missing: tika-app-${project.version}.zip">
<condition><not><available file="${basedir}/target/${project.version}/tika-app-${project.version}.zip" /></not></condition>
</fail>
<fail message="Release staging missing: tika-server-standard-${project.version}.zip">
<condition><not><available file="${basedir}/target/${project.version}/tika-server-standard-${project.version}.zip" /></not></condition>
</fail>
<fail message="Release staging missing: tika-eval-app-${project.version}.zip">
<condition><not><available file="${basedir}/target/${project.version}/tika-eval-app-${project.version}.zip" /></not></condition>
</fail>
<!--
pipes plugin zips are staged via a glob, so assert the
staged count equals the number of plugin modules that have
an assembly descriptor. This catches a single plugin whose
zip silently dropped out without hard-coding the plugin set.
-->
<resourcecount property="staged.plugin.zip.count">
<fileset dir="${basedir}/target/${project.version}" includes="tika-pipes-*-${project.version}.zip" />
</resourcecount>
<resourcecount property="source.plugin.count">
<fileset dir="${basedir}/tika-pipes/tika-pipes-plugins" includes="*/src/main/assembly/assembly.xml" />
</resourcecount>
<fail message="Release staging has ${staged.plugin.zip.count} tika-pipes plugin zip(s) but there are ${source.plugin.count} plugin module(s) with an assembly descriptor; a plugin zip was dropped from dist staging.">
<condition><not><equals arg1="${staged.plugin.zip.count}" arg2="${source.plugin.count}" /></not></condition>
</fail>
<checksum algorithm="SHA-512" fileext=".sha512">
<fileset dir="${basedir}/target/${project.version}">
<include name="*.tgz" />
<include name="*.zip" />
<include name="*.?ar" />
</fileset>
</checksum>
<checksum file="${basedir}/target/${project.version}/tika-${project.version}-src.zip" algorithm="SHA-512" property="checksum" />
<!-- this spacing is less than ideal, but if you indent here, the vote.txt file will have the leading spaces -->
<echo file="${basedir}/target/vote.txt">
From: ${username}@apache.org
To: dev@tika.apache.org
user@tika.apache.org
Subject: [VOTE] Release Apache Tika ${project.version} Candidate #N
A candidate for the Tika ${project.version} release is available at:
https://dist.apache.org/repos/dist/dev/tika/${project.version}
The release candidate is a zip archive of the sources in:
https://github.com/apache/tika/tree/{project.version}-rcN/
The SHA-512 checksum of the archive is
${checksum}.
In addition, a staged maven repository is available here:
https://repository.apache.org/content/repositories/orgapachetika-.../org/apache/tika
Please vote on releasing this package as Apache Tika ${project.version}.
The vote is open for the next 72 hours and passes if a majority of at
least three +1 Tika PMC votes are cast.
[ ] +1 Release this package as Apache Tika ${project.version}
[ ] -1 Do not release this package because...${line.separator}
</echo>
<echo />
<echo>
The release candidate has been prepared in:
${basedir}/target/${project.version}
Please deploy it to people.apache.org like this:
scp -r ${basedir}/target/${project.version} people.apache.org:public_html/tika/
A release vote template has been generated for you:
file://${basedir}/target/vote.txt
</echo>
<echo />
</target>
</configuration>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>org.apache.ant</groupId>
<artifactId>ant-nodeps</artifactId>
<version>1.8.1</version>
</dependency>
</dependencies>
</plugin>
</plugins>
</build>
</profile>
</profiles>
<build>
<plugins>
<plugin>
<groupId>org.apache.rat</groupId>
<artifactId>apache-rat-plugin</artifactId>
<configuration>
<inputExcludes>
<inputExclude>CHANGES.txt</inputExclude>
<inputExclude>README.md</inputExclude>
<!-- remove this once we figure out the bundle packaging -->
<inputExclude>tika-bundle/src/main/resources/META-INF/MANIFEST.MF</inputExclude>
<inputExclude>.gitattributes</inputExclude>
<!-- Antora UI supplemental files -->
<inputExclude>docs/supplemental-ui/**</inputExclude>
<!-- subprojects already checked, added for RAT 0.17, see also RAT-97 -->
<inputExclude>tika-*/**</inputExclude>
</inputExcludes>
</configuration>
</plugin>
</plugins>
</build>
<description>The Apache Tika™ toolkit detects and extracts metadata and structured text content from various documents
using existing parser libraries.
</description>
<organization>
<name>The Apache Software Foundation</name>
<url>https://www.apache.org</url>
</organization>
<issueManagement>
<system>JIRA</system>
<url>https://issues.apache.org/jira/browse/TIKA</url>
</issueManagement>
<ciManagement>
<system>Jenkins</system>
<url>https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/</url>
</ciManagement>
<scm>
<tag>3.0.0-rc1</tag>
</scm>
</project>