laomo-hub commented on PR #7688:
URL: https://github.com/apache/shenyu/pull/7688#issuecomment-6247224279
Thanks for the review! The 2.41.0 request comes from Gson 2.13.2. I reran
the dependency tree with the current PR POM and JDK 17:
```sh
./mvnw -B -ntp -pl shenyu-common -am \
org.apache.maven.plugins:maven-dependency-plugin:3.8.1:tree \
-Dincludes=com.google.errorprone:error_prone_annotations -Dverbose=true
```
Relevant output:
```text
org.apache.shenyu:shenyu-common:jar:2.7.2-SNAPSHOT
+- com.google.code.gson:gson:jar:2.13.2:compile
| \- com.google.errorprone:error_prone_annotations:jar:2.41.0:compile
(version managed from 2.41.0)
+- com.github.ben-manes.caffeine:caffeine:jar:2.9.3:compile
| \- (com.google.errorprone:error_prone_annotations:jar:2.41.0:compile -
version managed from 2.10.0; omitted for duplicate)
\- com.google.guava:guava:jar:32.0.0-jre:compile
\- (com.google.errorprone:error_prone_annotations:jar:2.41.0:compile -
version managed from 2.18.0; omitted for duplicate)
```
The command completed successfully for all four selected projects. My local
invocation used `mvnw.cmd` and the existing Maven cache in offline mode. The
original pre-change Enforcer log also shows Gson requesting 2.41.0, so this
aligns with an existing request rather than choosing a newer version
independently.
I've updated the description to name the requesters, note that projects
inheriting the parent inherit these managed versions, and remove the stale
Draft sentence. The Windows note is complete: a short
`jdk.net.unixdomain.tmpdir` was set only for the build processes to work around
a local JDK loopback error; no repository or system configuration was changed.
The code is still at `6d26484f`. Its 8 workflows are awaiting approval.
Could you please approve them to run, including the full `pr_build`? The local
full-reactor attempt and its baseline failures remain documented in the
description.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
