-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathpom.xml
More file actions
292 lines (277 loc) · 12.4 KB
/
pom.xml
File metadata and controls
292 lines (277 loc) · 12.4 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
289
290
291
292
<?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.qubiton</groupId>
<artifactId>qubiton-sdk</artifactId>
<!--
Release-bump procedure: when cutting a Maven Central release, drop the
`-SNAPSHOT` suffix (e.g. set <version>0.1.0</version>), tag the commit
as `v0.1.0`, run `mvn -P release deploy`, then bump the next development
line (e.g. `0.2.0-SNAPSHOT`) on develop. Day-to-day builds stay on the
snapshot version so consumers can pin pre-release builds.
-->
<version>0.1.0-SNAPSHOT</version>
<packaging>jar</packaging>
<name>QubitOn API SDK</name>
<description>Java SDK for the QubitOn API by QubitOn — validate addresses, tax IDs, bank accounts; look up business registrations; screen for sanctions and disqualified directors; and access 40+ enrichment endpoints across 250+ countries.</description>
<url>https://www.qubiton.com</url>
<organization>
<name>QubitOn</name>
<url>https://www.qubiton.com</url>
</organization>
<licenses>
<license>
<name>MIT License</name>
<url>https://opensource.org/licenses/MIT</url>
<distribution>repo</distribution>
</license>
</licenses>
<developers>
<developer>
<id>qubiton</id>
<name>QubitOn Engineering</name>
<email>support@qubiton.com</email>
<organization>QubitOn</organization>
<organizationUrl>https://www.qubiton.com</organizationUrl>
<url>https://www.qubiton.com</url>
</developer>
</developers>
<!--
Public-facing SCM URLs.
The Java SDK source lives at https://gitea.apexanalytix.app/data/portal in
the `sdks/java/` subdirectory of the QubitOn portal monorepo. For Maven Central
publishing the canonical SCM URLs reference a public mirror at
github.com/qubitonhq/qubiton-java-sdk — keep these URLs in sync with whatever
public mirror is set up for releases. If no public mirror exists yet, replace
the URLs below with the internal Gitea coordinates and remove the
<issueManagement> block.
-->
<scm>
<connection>scm:git:https://github.com/qubitonhq/qubiton-java-sdk.git</connection>
<developerConnection>scm:git:ssh://git@github.com/qubitonhq/qubiton-java-sdk.git</developerConnection>
<url>https://github.com/qubitonhq/qubiton-java-sdk</url>
<tag>HEAD</tag>
</scm>
<issueManagement>
<system>GitHub Issues</system>
<url>https://github.com/qubitonhq/qubiton-java-sdk/issues</url>
</issueManagement>
<properties>
<maven.compiler.release>11</maven.compiler.release>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
<jackson.bom.version>2.18.0</jackson.bom.version>
<junit.version>5.11.0</junit.version>
</properties>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>com.fasterxml.jackson</groupId>
<artifactId>jackson-bom</artifactId>
<version>${jackson.bom.version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
<dependencies>
<dependency>
<groupId>com.fasterxml.jackson.core</groupId>
<artifactId>jackson-databind</artifactId>
</dependency>
<dependency>
<groupId>com.fasterxml.jackson.core</groupId>
<artifactId>jackson-annotations</artifactId>
</dependency>
<!--
JSR-310 module — provides LocalDate / LocalDateTime / Instant deserialisation,
required by Risk.CreditAnalysisResponse.dateOfDecisioning and any future
response DTO that exposes a java.time type. Registered automatically by
QubitOnClientBuilder.objectMapper() when present.
-->
<dependency>
<groupId>com.fasterxml.jackson.datatype</groupId>
<artifactId>jackson-datatype-jsr310</artifactId>
</dependency>
<!-- Test dependencies -->
<dependency>
<groupId>org.junit.jupiter</groupId>
<artifactId>junit-jupiter-api</artifactId>
<version>${junit.version}</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.junit.jupiter</groupId>
<artifactId>junit-jupiter-engine</artifactId>
<version>${junit.version}</version>
<scope>test</scope>
</dependency>
</dependencies>
<!--
Maven Central publishing is handled by the Sonatype `central-publishing-maven-plugin`
in the `release` profile (replacing the legacy OSSRH staging flow). No explicit
`distributionManagement` block is needed for the new Central Portal — the plugin
manages staging and release on its own. See the `release` profile below.
-->
<build>
<!--
Resource filtering injects @project.version@ into qubiton-sdk-version.properties at
build time so QubitOnClient.SDK_VERSION reflects the published Maven version
without a manual hardcoded constant.
-->
<resources>
<resource>
<directory>src/main/resources</directory>
<filtering>true</filtering>
<includes>
<include>qubiton-sdk-version.properties</include>
</includes>
</resource>
<resource>
<directory>src/main/resources</directory>
<filtering>false</filtering>
<excludes>
<exclude>qubiton-sdk-version.properties</exclude>
</excludes>
</resource>
</resources>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.13.0</version>
<configuration>
<release>${maven.compiler.release}</release>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<version>3.3.1</version>
<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>
<version>3.10.0</version>
<executions>
<execution>
<id>attach-javadocs</id>
<goals><goal>jar</goal></goals>
</execution>
</executions>
<configuration>
<source>11</source>
<quiet>true</quiet>
<!--
Doclint is enabled (Maven default) so missing/malformed Javadoc is
surfaced as build warnings instead of being suppressed silently.
Demote a couple of low-value categories to keep the build green
without hiding genuine errors.
-->
<additionalOptions>
<additionalOption>-Xdoclint:all,-missing,-syntax</additionalOption>
</additionalOptions>
<failOnError>false</failOnError>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<version>3.4.1</version>
<configuration>
<archive>
<!--
NOTE on `Implementation-Version`:
QubitOnClient.readSdkVersion() prefers a filtered properties resource
(`qubiton-sdk-version.properties`) and only falls back to
Package.getImplementationVersion() if the resource is missing. If a
consumer shades or relocates this jar (e.g. uberjar bundling), the
shaded jar's manifest will carry the shader's version, not ours —
but the version.properties resource survives shading because it's
on the classpath under our package's resource root. Keep both
entries enabled; the properties path is the source of truth.
-->
<manifest>
<addDefaultImplementationEntries>true</addDefaultImplementationEntries>
<addDefaultSpecificationEntries>true</addDefaultSpecificationEntries>
</manifest>
<manifestEntries>
<Automatic-Module-Name>com.qubiton.sdk</Automatic-Module-Name>
</manifestEntries>
</archive>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>3.2.5</version>
</plugin>
<!--
GPG signing for Maven Central. Skipped by default to keep local builds simple.
Activate with `-P release` and provide GPG keys via your environment.
-->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-gpg-plugin</artifactId>
<version>3.2.4</version>
<executions>
<execution>
<id>sign-artifacts</id>
<phase>verify</phase>
<goals><goal>sign</goal></goals>
<configuration>
<skip>true</skip>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
<profiles>
<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>false</skip>
</configuration>
</execution>
</executions>
</plugin>
<!--
Sonatype Central Publishing Plugin (replacement for the legacy
nexus-staging-maven-plugin). Required for Maven Central publish to
actually work after the OSSRH → Central Portal migration.
Activated only on `-P release` so day-to-day builds don't pull it.
-->
<plugin>
<groupId>org.sonatype.central</groupId>
<artifactId>central-publishing-maven-plugin</artifactId>
<version>0.6.0</version>
<extensions>true</extensions>
<configuration>
<publishingServerId>central</publishingServerId>
<autoPublish>false</autoPublish>
</configuration>
</plugin>
</plugins>
</build>
</profile>
</profiles>
</project>