This is an automated email from the ASF dual-hosted git repository. davsclaus pushed a commit to branch quick-fix/pin-aliyun-tea in repository https://gitbox.apache.org/repos/asf/camel.git
commit a586938423b5674243d240b03eaf621fe16a9649 Author: Claus Ibsen <[email protected]> AuthorDate: Tue Sep 15 09:03:49 2026 +0200 chore: pin com.aliyun:tea so the Alibaba components do not resolve an open version range The Alibaba SDK poms declare com.aliyun:tea as [1.x, 2.0.0) ranges, which forces Maven to fetch remote metadata on every build and fails with "No versions available" whenever that fetch fails or the build is offline. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Signed-off-by: Claus Ibsen <[email protected]> --- parent/pom.xml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/parent/pom.xml b/parent/pom.xml index 36ac3fa0d241..1437aff93237 100644 --- a/parent/pom.xml +++ b/parent/pom.xml @@ -74,6 +74,8 @@ <aliyun-eventbridge-client-version>1.3.14</aliyun-eventbridge-client-version> <aliyun-tablestore-version>5.17.13</aliyun-tablestore-version> <tea-openapi-version>0.3.15</tea-openapi-version> + <!-- the Alibaba SDKs declare com.aliyun:tea as an open version range, so it is pinned in dependencyManagement --> + <tea-version>1.4.2</tea-version> <amazon-kinesis-client-version>3.5.2</amazon-kinesis-client-version> <angus-mail-version>2.0.5</angus-mail-version> <apacheds-version>2.0.0.AM27</apacheds-version> @@ -742,6 +744,11 @@ <artifactId>sls20201230</artifactId> <version>${aliyun-sls-version}</version> </dependency> + <dependency> + <groupId>com.aliyun</groupId> + <artifactId>tea</artifactId> + <version>${tea-version}</version> + </dependency> <dependency> <groupId>com.aliyun</groupId> <artifactId>tea-openapi</artifactId>
