-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathpom.xml
More file actions
268 lines (250 loc) · 10.1 KB
/
Copy pathpom.xml
File metadata and controls
268 lines (250 loc) · 10.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
<?xml version="1.0" encoding="UTF-8"?>
<!--
The aggregator. Nothing is built here; what is here is the version
every module moves on, the plugin versions every module uses, and the
compiler settings that are the same everywhere.
The engine, the C ABI and this client move on one version number, so
the version below is the engine's and is not chosen here.
-->
<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>
<groupId>dev.zudb</groupId>
<artifactId>zudb-parent</artifactId>
<version>0.11.0-SNAPSHOT</version>
<packaging>pom</packaging>
<name>zu for the JVM</name>
<description>The Java client for zu, an embedded property-graph database.</description>
<url>https://github.com/tamnd/zu-java</url>
<licenses>
<license>
<name>Apache-2.0</name>
<url>https://www.apache.org/licenses/LICENSE-2.0.txt</url>
</license>
</licenses>
<developers>
<developer>
<id>tamnd</id>
<name>Tam Nguyen Duc</name>
<url>https://github.com/tamnd</url>
</developer>
</developers>
<scm>
<connection>scm:git:https://github.com/tamnd/zu-java.git</connection>
<developerConnection>scm:git:ssh://git@github.com/tamnd/zu-java.git</developerConnection>
<url>https://github.com/tamnd/zu-java</url>
</scm>
<issueManagement>
<system>GitHub</system>
<url>https://github.com/tamnd/zu-java/issues</url>
</issueManagement>
<modules>
<module>zudb</module>
<module>zudb-tck</module>
<module>zudb-ffm</module>
<module>zudb-corpus</module>
<module>zudb-jni</module>
<module>zudb-arrow</module>
<module>zudb-bench</module>
</modules>
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
<!-- A fixed timestamp is what makes two builds of one commit byte
for byte the same jar, which is the only way a user can check
that what is on Maven Central is what is in this repository. -->
<project.build.outputTimestamp>2026-01-01T00:00:00Z</project.build.outputTimestamp>
<!-- Where the API is compiled to. 17 is the floor because it is the
oldest release still getting updates, and because an SDK that
needs a recent JDK in 2026 is an SDK a large part of the
enterprise ecosystem cannot adopt. -->
<zu.release.api>17</zu.release.api>
<!-- Where the FFM provider is compiled to. The Foreign Function and
Memory API was finalised in 22, but 22 has been end of life
since September 2024 and the current long-term release is 25,
so 25 is what this targets. -->
<zu.release.ffm>25</zu.release.ffm>
<!-- Anything a run wants to hand the test JVM on top of what the
build already passes it, so that CI can add assertions without
restating the flags the suite cannot run without. -->
<zu.test.args></zu.test.args>
<!-- arrow-java, named in one module and nowhere else. It moves on
its own schedule and an application usually pins its own, which
is the other reason the Arrow reader is an artifact of its own
rather than a package in the client. -->
<arrow.version>19.0.0</arrow.version>
<junit.version>6.1.3</junit.version>
<maven.compiler.plugin.version>3.15.0</maven.compiler.plugin.version>
<maven.surefire.plugin.version>3.5.6</maven.surefire.plugin.version>
<maven.jar.plugin.version>3.5.1</maven.jar.plugin.version>
<maven.dependency.plugin.version>3.8.1</maven.dependency.plugin.version>
<maven.source.plugin.version>3.4.0</maven.source.plugin.version>
<maven.javadoc.plugin.version>3.12.0</maven.javadoc.plugin.version>
<maven.shade.plugin.version>3.6.2</maven.shade.plugin.version>
<maven.enforcer.plugin.version>3.6.2</maven.enforcer.plugin.version>
<maven.gpg.plugin.version>3.2.8</maven.gpg.plugin.version>
<central.publishing.plugin.version>0.11.0</central.publishing.plugin.version>
</properties>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>dev.zudb</groupId>
<artifactId>zudb</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>dev.zudb</groupId>
<artifactId>zudb-tck</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>org.apache.arrow</groupId>
<artifactId>arrow-bom</artifactId>
<version>${arrow.version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
<dependency>
<groupId>org.junit</groupId>
<artifactId>junit-bom</artifactId>
<version>${junit.version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
<dependencies>
<dependency>
<groupId>org.junit.jupiter</groupId>
<artifactId>junit-jupiter</artifactId>
<scope>test</scope>
</dependency>
</dependencies>
<build>
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>${maven.compiler.plugin.version}</version>
<configuration>
<compilerArgs>
<!-- Every warning, and a warning is a failure. A binding
that crosses into native memory is the last place to
be relaxed about a rawtype or a missing override. -->
<arg>-Xlint:all,-requires-automatic,-requires-transitive-automatic</arg>
<arg>-Werror</arg>
</compilerArgs>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>${maven.surefire.plugin.version}</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<version>${maven.jar.plugin.version}</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<version>${maven.dependency.plugin.version}</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<version>${maven.source.plugin.version}</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>${maven.javadoc.plugin.version}</version>
</plugin>
</plugins>
</pluginManagement>
</build>
<profiles>
<!-- The libraries, which are downloaded rather than compiled, so an
ordinary build has no business needing them and does not build
this module. scripts/stage-natives.sh fills zudb-native/lib
first; CI passes this after it has run. -->
<profile>
<id>natives</id>
<modules>
<module>zudb-native</module>
</modules>
</profile>
<!-- Sources, javadoc and signatures, which Maven Central requires
and a local build has no use for. -->
<profile>
<id>release</id>
<properties>
<!-- gpg reads a passphrase from a terminal, and a release runs
where there is none. Loopback is what makes it read the one
the plugin hands it instead of trying to open a tty and
hanging until the job is cancelled. -->
<gpg.args>--pinentry-mode=loopback</gpg.args>
</properties>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-gpg-plugin</artifactId>
<version>${maven.gpg.plugin.version}</version>
<executions>
<execution>
<id>sign-artifacts</id>
<phase>verify</phase>
<goals><goal>sign</goal></goals>
</execution>
</executions>
</plugin>
<!-- One upload for the whole reactor rather than one per
module, so that a release either lands complete or does
not land: Central validates a deployment as a unit, and a
half-published version is a version nobody can use and
nobody can replace. autoPublish is off, so a deployment
waits in the portal until a human looks at it. -->
<plugin>
<groupId>org.sonatype.central</groupId>
<artifactId>central-publishing-maven-plugin</artifactId>
<version>${central.publishing.plugin.version}</version>
<extensions>true</extensions>
<configuration>
<publishingServerId>central</publishingServerId>
<autoPublish>false</autoPublish>
<waitUntil>validated</waitUntil>
<excludeArtifacts>
<excludeArtifact>zudb-bench</excludeArtifact>
<excludeArtifact>zudb-tck</excludeArtifact>
</excludeArtifacts>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<executions>
<execution>
<id>attach-sources</id>
<goals><goal>jar-no-fork</goal></goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<executions>
<execution>
<id>attach-javadocs</id>
<goals><goal>jar</goal></goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
</profiles>
</project>