Repository navigation
Expand file tree
/
Copy pathpom.xml
More file actions
269 lines (252 loc) · 9.82 KB
/
Copy pathpom.xml
File metadata and controls
269 lines (252 loc) · 9.82 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
<?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>
<groupId>com.clickhouse.chdb</groupId>
<artifactId>chdb-java-parent</artifactId>
<version>1.1.0</version>
<packaging>pom</packaging>
<name>chDB Java Binding (parent)</name>
<description>JDBC driver and native platform packages for the embedded chDB engine.</description>
<url>https://github.com/chdb-io/chdb-java</url>
<licenses>
<license>
<name>Apache License, Version 2.0</name>
<url>https://www.apache.org/licenses/LICENSE-2.0.txt</url>
</license>
</licenses>
<organization>
<name>chDB</name>
<url>https://chdb.io</url>
</organization>
<!--
Central rejects a release without <scm>, <developers> and <licenses>. They are here rather
than in the release profile because they describe the project whether or not it is being
published, and a consumer reading the POM from a snapshot should see the same thing.
-->
<scm>
<connection>scm:git:https://github.com/chdb-io/chdb-java.git</connection>
<developerConnection>scm:git:git@github.com:chdb-io/chdb-java.git</developerConnection>
<url>https://github.com/chdb-io/chdb-java</url>
<tag>HEAD</tag>
</scm>
<developers>
<developer>
<id>chdb-io</id>
<name>The chDB maintainers</name>
<url>https://github.com/chdb-io</url>
<organization>chDB</organization>
<organizationUrl>https://chdb.io</organizationUrl>
</developer>
</developers>
<issueManagement>
<system>GitHub Issues</system>
<url>https://github.com/chdb-io/chdb-java/issues</url>
</issueManagement>
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
<!-- Java 11 is the V1 floor (work plan section 2.1). Never raise without a plan change. -->
<maven.compiler.release>11</maven.compiler.release>
<!--
Engine baseline. These three coordinates are the single source of truth for
which chDB Core release this binding is built and tested against; scripts/engine.properties
mirrors them for the shell/CMake side. Changing engine.version requires a new
Maven version (work plan section 4.3) and a full platform re-test.
-->
<chdb.engine.version>26.11.1</chdb.engine.version>
<chdb.binding.revision>1</chdb.binding.revision>
<!-- Bumped only on an incompatible change to the Java <-> JNI shim contract. -->
<chdb.jni.abi.version>5</chdb.jni.abi.version>
<!-- Bumped only on an incompatible change to the public Java API. -->
<chdb.java.api.version>1</chdb.java.api.version>
<arrow.java.version>19.0.0</arrow.java.version>
<junit.version>5.10.2</junit.version>
<surefire.version>3.2.5</surefire.version>
<failsafe.version>3.2.5</failsafe.version>
<!-- Internal reactor POMs are never published; the six library modules opt in. -->
<maven.deploy.skip>true</maven.deploy.skip>
</properties>
<modules>
<module>chdb-bom</module>
<module>chdb-jdbc</module>
<module>chdb-arrow</module>
<module>chdb-native-macos-aarch64</module>
<module>chdb-native-macos-x86_64</module>
<module>chdb-native-linux-x86_64-gnu</module>
<module>chdb-native-linux-aarch64-gnu</module>
<module>chdb-integration-tests</module>
<module>chdb-examples</module>
</modules>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.junit</groupId>
<artifactId>junit-bom</artifactId>
<version>${junit.version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
<build>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>flatten-maven-plugin</artifactId>
<version>1.7.3</version>
<configuration>
<flattenMode>ossrh</flattenMode>
<flattenDependencyMode>inherited</flattenDependencyMode>
<pomElements>
<!-- Do not leak the Central publishing extension into consumer builds. -->
<build>remove</build>
<repositories>remove</repositories>
<pluginRepositories>remove</pluginRepositories>
</pomElements>
</configuration>
<executions>
<execution>
<id>flatten-consumer-pom</id>
<phase>process-resources</phase>
<goals><goal>flatten</goal></goals>
</execution>
<execution>
<id>clean-consumer-pom</id>
<phase>clean</phase>
<goals><goal>clean</goal></goals>
</execution>
</executions>
</plugin>
</plugins>
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.13.0</version>
<configuration>
<compilerArgs>
<arg>-Xlint:all</arg>
<!-- The JDBC interfaces we implement are stable; serial/this-escape noise is not useful. -->
<arg>-Xlint:-serial</arg>
</compilerArgs>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>${surefire.version}</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-failsafe-plugin</artifactId>
<version>${failsafe.version}</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<version>3.4.1</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<version>3.3.1</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>3.6.3</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<version>3.1.0</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-resources-plugin</artifactId>
<version>3.3.1</version>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>exec-maven-plugin</artifactId>
<version>3.2.0</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-gpg-plugin</artifactId>
<version>3.2.8</version>
</plugin>
<plugin>
<groupId>org.sonatype.central</groupId>
<artifactId>central-publishing-maven-plugin</artifactId>
<version>0.12.0</version>
</plugin>
</plugins>
</pluginManagement>
</build>
<profiles>
<!--
Everything a Maven Central release needs and an ordinary build must not pay for: signing
(which prompts for a passphrase), and the publishing plugin (which talks to Sonatype).
The source and javadoc jars Central also requires are attached per module, because what
"sources" means differs between the driver and a package whose content is two shared
libraries — see the release profile in each module.
mvn -Prelease deploy
Requires a `central` server entry in settings.xml holding the portal token, and a GPG
key whose public half is on a keyserver. docs/publishing.md is the runbook.
-->
<profile>
<id>release</id>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-gpg-plugin</artifactId>
<executions>
<execution>
<id>sign-artifacts</id>
<phase>verify</phase>
<goals>
<goal>sign</goal>
</goals>
<configuration>
<skip>${maven.deploy.skip}</skip>
<!--
Loopback pinentry so the passphrase can come from a CI secret rather than a
terminal. Harmless interactively: gpg-agent still caches as usual.
-->
<gpgArguments>
<arg>--pinentry-mode</arg>
<arg>loopback</arg>
</gpgArguments>
</configuration>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.sonatype.central</groupId>
<artifactId>central-publishing-maven-plugin</artifactId>
<extensions>true</extensions>
<configuration>
<publishingServerId>central</publishingServerId>
<skipPublishing>${maven.deploy.skip}</skipPublishing>
<checksums>required</checksums>
<!--
Deliberately not automatic. A release here spans six library modules
and hundreds of megabytes, and cannot be unpublished; a human
confirming the bundle in the portal is worth the
extra step, at least until several releases have gone out uneventfully.
-->
<autoPublish>false</autoPublish>
<!-- Upload success means validated and waiting for manual Portal approval. -->
<waitUntil>VALIDATED</waitUntil>
</configuration>
</plugin>
</plugins>
</build>
</profile>
</profiles>
</project>