Repository navigation
Expand file tree
/
Copy pathpom.xml
More file actions
413 lines (388 loc) · 18.3 KB
/
Copy pathpom.xml
File metadata and controls
413 lines (388 loc) · 18.3 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
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
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
<?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.openjiuwen</groupId>
<artifactId>agent-runtime-java</artifactId>
<version>${revision}</version>
<packaging>pom</packaging>
<name>agent-runtime-java</name>
<description>Agent Runtime Java - A2A Service and Agent Service Adapters</description>
<parent>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-parent</artifactId>
<version>4.0.7</version>
<relativePath/>
</parent>
<modules>
<module>service</module>
</modules>
<properties>
<revision>0.1.4</revision>
<java.version>17</java.version>
<maven.compiler.source>17</maven.compiler.source>
<maven.compiler.target>17</maven.compiler.target>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<a2a-sdk.version>1.0.0.Final</a2a-sdk.version>
<!-- Agent Core:Maven 版本与本地源码分支,文档仅引用此处,勿在多处写死版本号 -->
<agent-core.version>0.1.17</agent-core.version>
<agent-core.git.branch>develop</agent-core.git.branch>
<agent-core.repo.url>https://gitcode.com/openJiuwen/agent-core-java</agent-core.repo.url>
<!--
============ 依赖版本归一:与 agent-core-java 严格一致 ============
以下属性显式覆盖 spring-boot-dependencies 4.0.7 的同名属性(parent 的
dependencyManagement 优先于传递依赖,若不做覆盖,runtime 实际解析版本
会被 Boot BOM 抬升/压降,与 core 不一致)。取值与 agent-core-java/pom.xml
<properties> 完全对齐;若 core 调整版本,此处需同步更新。
历史例外项(均已通过升级 core 消除,两边现在严格一致):
- reactor:core 已升 3.8.6(=Boot 的 reactor-bom 2025.0.6),无需再覆盖。
- protobuf:core 已升 4.33.2(a2a-sdk 1.0.0.Final 由 protoc 4.x 生成),
下方 dependencyManagement 的 pin 与 core 值一致,保留作显式声明。
- junit-jupiter:core 已升 6.0.3(=Boot 管理值),两边一致。
- jackson-annotations:core 已升 jackson-bom 2.21.5,annotations 随 BOM
为 2.21(含 a2a-sdk 需要的 JsonSerializeAs),不再需要单独 pin。
- jedis:core 已升 7.0.0(=Boot 管理值),不再覆盖。
- bouncy-castle:Memory 拆包前 core 直接引入 bcprov 1.85;拆包后
bcprov 只会经 pulsar 回落到 1.84,因此 runtime 继续锁定 1.85。
gson 例外:core 未声明 gson;a2a-sdk 需 2.11.0+,runtime 独立 pin 2.11.0,
见下方 dependencyManagement。
对齐范围约定:仅对 main/compile 运行时依赖严格一致;test scope 组件
(如 surefire/maven 插件自带带入的 byte-buddy 1.18.3、spring-boot-test
传递的测试侧依赖)不纳入对齐,有风险/改动大的保持现状即可。
-->
<jackson-2-bom.version>2.21.5</jackson-2-bom.version>
<!-- opentelemetry:core 声明 1.64.0,Boot 4.0.7 BOM 管理 1.55.0 会压降 core 传递的 OTel,
导致 runtime 侧 OTel 版本与 core 不一致(潜在 NoSuchMethodError 风险)。覆盖为 1.64.0 对齐 core。 -->
<opentelemetry.version>1.64.0</opentelemetry.version>
<!-- jedis:core 已升 7.0.0(=Boot 管理值),无需覆盖 -->
<!-- <jedis.version>5.1.5</jedis.version> -->
<pulsar.version>4.2.3</pulsar.version>
<bouncy-castle.version>1.85</bouncy-castle.version>
<mockito.version>5.14.2</mockito.version>
<!-- byte-buddy:main scope 对齐 core 1.15.11;test 侧 surefire 插件自带 1.18.3,
属测试组件差异,不纳入对齐(约定见上方注释) -->
<byte-buddy.version>1.15.11</byte-buddy.version>
<snakeyaml.version>2.2</snakeyaml.version>
<slf4j.version>2.0.12</slf4j.version>
<logback.version>1.5.37</logback.version>
<assertj.version>3.27.7</assertj.version>
<commons-lang3.version>3.18.0</commons-lang3.version>
<commons-codec.version>1.20.0</commons-codec.version>
<postgresql.version>42.7.12</postgresql.version>
<mysql.version>9.7.0</mysql.version>
<h2.version>2.2.224</h2.version>
<sqlite-jdbc.version>3.53.2.1</sqlite-jdbc.version>
<lombok.version>1.18.32</lombok.version>
<log4j2.version>2.26.1</log4j2.version>
<kotlin.version>2.4.10</kotlin.version>
<!-- okhttp:Boot 4 BOM 不管理,adapters-common 直接依赖,pin 在此供统一管控 -->
<okhttp.version>4.12.0</okhttp.version>
</properties>
<dependencyManagement>
<dependencies>
<!-- A2A SDK (v1.0.0.Final: groupId changed from io.github.a2asdk to org.a2aproject.sdk) -->
<dependency>
<groupId>org.a2aproject.sdk</groupId>
<artifactId>a2a-java-sdk-spec</artifactId>
<version>1.0.0.Final</version>
</dependency>
<dependency>
<groupId>org.a2aproject.sdk</groupId>
<artifactId>a2a-java-sdk-server-common</artifactId>
<version>1.0.0.Final</version>
</dependency>
<dependency>
<groupId>org.a2aproject.sdk</groupId>
<artifactId>a2a-java-sdk-jsonrpc-common</artifactId>
<version>1.0.0.Final</version>
</dependency>
<dependency>
<groupId>org.a2aproject.sdk</groupId>
<artifactId>a2a-java-sdk-client</artifactId>
<version>1.0.0.Final</version>
</dependency>
<!-- OpenJiuwen Agent Core -->
<dependency>
<groupId>com.openjiuwen</groupId>
<artifactId>agent-core-java</artifactId>
<version>0.1.17</version>
</dependency>
<!-- ② Service leaf modules(${revision} 是 CI-friendly,flatten 会展开为字面值) -->
<dependency>
<groupId>com.openjiuwen</groupId>
<artifactId>agent-service-spec</artifactId>
<version>${revision}</version>
</dependency>
<dependency>
<groupId>com.openjiuwen</groupId>
<artifactId>agent-service-adapters-common</artifactId>
<version>${revision}</version>
</dependency>
<dependency>
<groupId>com.openjiuwen</groupId>
<artifactId>agent-service-adapters-agentcore</artifactId>
<version>${revision}</version>
</dependency>
<dependency>
<groupId>com.openjiuwen</groupId>
<artifactId>agent-service-app</artifactId>
<version>${revision}</version>
</dependency>
<!--
Gson / Protobuf:
- protobuf:core 已升 4.33.2,此处显式声明与 core 严格一致
(a2a-sdk 1.0.0.Final 内部用 protoc 4.x 生成,protobuf 3.x 会
在运行期抛 NoSuchMethodError/二进制不兼容)。
- gson:core 未声明 gson;a2a-sdk 的 JSONRPCUtils 需要 2.11.0+
(setStrictness API),故 pin 2.11.0(显式声明优先于 Boot)。
-->
<dependency>
<groupId>com.google.code.gson</groupId>
<artifactId>gson</artifactId>
<version>2.11.0</version>
</dependency>
<dependency>
<groupId>com.google.protobuf</groupId>
<artifactId>protobuf-java</artifactId>
<version>4.33.2</version>
</dependency>
<dependency>
<groupId>com.google.protobuf</groupId>
<artifactId>protobuf-java-util</artifactId>
<version>4.33.2</version>
</dependency>
<!--
============ 对外版本锁(BOM 传播)============
以下条目对应 <properties> 里覆盖 Boot BOM 的同名属性。
原先只靠 properties 覆盖,仅在 runtime 自身构建期生效;一旦消费方
import runtime BOM,properties 不传播 → 消费方拿不到版本 pin →
被 Boot BOM 原始值或 nearest-wins 仲裁覆盖,导致运行期版本不一致
(如 protobuf 被 milvus 路径压降、slf4j/otel 被 Boot BOM 压降)。
显式声明在此处,install 后 POM 的 depMgmt 保留字面条目,消费方
import 时内联到其有效 depMgmt,版本锁随之传播。
flattenMode=resolveCiFriendliesOnly 只展开 ${revision}/${sha1}/
${changelist} 三个 CI-friendly 占位符,不展开 ${xxx.version} 等
自定义属性。故此处版本必须用字面值,与 <properties> 里同名属性值
重复——这是 flatten 机制限制下的必要妥协(properties 保留用于
runtime 自身构建期覆盖 Boot BOM;depMgmt 字面值用于 BOM 传播到
消费方)。根治方案是拆独立 BOM 模块(方案 B),暂未实施。
scope 约定:
- 运行时依赖(slf4j/jackson/otel/snakeyaml/logback/postgresql/
mysql/h2/sqlite-jdbc/commons-lang3/commons-codec/pulsar/lombok/
okhttp)→ 不加 scope(compile),必须对消费方可见
- 纯测试依赖(mockito/assertj/byte-buddy)→ 加 scope=test,
消费方测试侧也能继承版本锁,但不污染其 compile classpath
- jackson-bom 用 import 引入整套 jackson 版本对齐
-->
<dependency>
<groupId>com.fasterxml.jackson</groupId>
<artifactId>jackson-bom</artifactId>
<version>2.21.5</version>
<type>pom</type>
<scope>import</scope>
</dependency>
<dependency>
<groupId>io.opentelemetry</groupId>
<artifactId>opentelemetry-bom</artifactId>
<version>1.64.0</version>
<type>pom</type>
<scope>import</scope>
</dependency>
<dependency>
<groupId>org.apache.pulsar</groupId>
<artifactId>pulsar-bom</artifactId>
<version>4.2.3</version>
<type>pom</type>
<scope>import</scope>
</dependency>
<dependency>
<groupId>org.jetbrains.kotlin</groupId>
<artifactId>kotlin-bom</artifactId>
<version>2.4.10</version>
<type>pom</type>
<scope>import</scope>
</dependency>
<!-- Keep bcprov at its pre-split version for consumers that only depend on Core. -->
<dependency>
<groupId>org.bouncycastle</groupId>
<artifactId>bcprov-jdk18on</artifactId>
<version>1.85</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
<version>2.0.12</version>
</dependency>
<dependency>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-classic</artifactId>
<version>1.5.37</version>
</dependency>
<dependency>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-core</artifactId>
<version>1.5.37</version>
</dependency>
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-api</artifactId>
<version>2.26.1</version>
</dependency>
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-core</artifactId>
<version>2.26.1</version>
</dependency>
<dependency>
<groupId>org.yaml</groupId>
<artifactId>snakeyaml</artifactId>
<version>2.2</version>
</dependency>
<dependency>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
<version>1.18.32</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-lang3</artifactId>
<version>3.18.0</version>
</dependency>
<dependency>
<groupId>commons-codec</groupId>
<artifactId>commons-codec</artifactId>
<version>1.20.0</version>
</dependency>
<dependency>
<groupId>org.postgresql</groupId>
<artifactId>postgresql</artifactId>
<version>42.7.12</version>
</dependency>
<dependency>
<groupId>com.mysql</groupId>
<artifactId>mysql-connector-j</artifactId>
<version>9.7.0</version>
</dependency>
<dependency>
<groupId>com.h2database</groupId>
<artifactId>h2</artifactId>
<version>2.2.224</version>
</dependency>
<dependency>
<groupId>org.xerial</groupId>
<artifactId>sqlite-jdbc</artifactId>
<version>3.53.2.1</version>
</dependency>
<dependency>
<groupId>com.squareup.okhttp3</groupId>
<artifactId>okhttp</artifactId>
<version>4.12.0</version>
</dependency>
<dependency>
<groupId>org.mockito</groupId>
<artifactId>mockito-core</artifactId>
<version>5.14.2</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.mockito</groupId>
<artifactId>mockito-junit-jupiter</artifactId>
<version>5.14.2</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>net.bytebuddy</groupId>
<artifactId>byte-buddy</artifactId>
<version>1.15.11</version>
</dependency>
<dependency>
<groupId>net.bytebuddy</groupId>
<artifactId>byte-buddy-agent</artifactId>
<version>1.15.11</version>
</dependency>
<dependency>
<groupId>org.assertj</groupId>
<artifactId>assertj-core</artifactId>
<version>3.27.7</version>
<scope>test</scope>
</dependency>
</dependencies>
</dependencyManagement>
<build>
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>${java.version}</source>
<target>${java.version}</target>
<annotationProcessorPaths>
<path>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
<version>1.18.32</version>
</path>
</annotationProcessorPaths>
</configuration>
</plugin>
</plugins>
</pluginManagement>
<plugins>
<!--
Required companion for the ${revision} CI-friendly version above: without it the installed/packaged
POMs keep the literal ${revision} and are unresolvable by downstream consumers. Bound to
process-resources so it runs under any command that reaches package/install/deploy (no build-command
change needed). resolveCiFriendliesOnly only rewrites ${revision}/${sha1}/${changelist}.
-->
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>flatten-maven-plugin</artifactId>
<version>1.6.0</version>
<configuration>
<updatePomFile>true</updatePomFile>
<flattenMode>resolveCiFriendliesOnly</flattenMode>
</configuration>
<executions>
<execution>
<id>flatten</id>
<phase>process-resources</phase>
<goals>
<goal>flatten</goal>
</goals>
</execution>
<execution>
<id>flatten.clean</id>
<phase>clean</phase>
<goals>
<goal>clean</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.jacoco</groupId>
<artifactId>jacoco-maven-plugin</artifactId>
<version>0.8.13</version>
<executions>
<execution>
<id>prepare-agent</id>
<goals>
<goal>prepare-agent</goal>
</goals>
</execution>
<execution>
<id>report</id>
<phase>test</phase>
<goals>
<goal>report</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
</project>