davsclaus opened a new pull request, #26452: URL: https://github.com/apache/camel/pull/26452
## Summary - `parent/pom.xml`: add a `tea-version` property (1.4.2) and a managed `com.aliyun:tea` entry in `dependencyManagement`. ## Why The Alibaba SDK poms pulled in by `camel-alibaba-fc`, `-sms`, `-kms`, `-sls` and `-eventbridge` (`credentials-java`, `openapiutil`, `alibabacloud-gateway-spi`, `darabonba-string`, ...) declare `com.aliyun:tea` as open version ranges such as `[1.1.14, 2.0.0)`. Resolving a range requires Maven to download `maven-metadata.xml` from Central on every build, and any failed/slow metadata fetch (or an offline build) fails with: ``` [ERROR] Failed to execute goal on project camel-alibaba-fc: Could not collect dependencies ... [ERROR] No versions available for com.aliyun:tea:jar:[1.1.14, 2.0.0) within specified range ``` even when all the 1.x jars are already in the local repository. Managing the version pins it and removes the metadata lookup entirely. 1.4.2 is the latest release on Central and the version `tea-openapi:0.3.15` (already managed here) depends on; the previous effective resolution was 1.3.1. ## Verification - `mvn -o dependency:tree -Dincludes=com.aliyun:tea` in the five affected modules resolves `com.aliyun:tea:jar:1.4.2` offline. - `mvn install` of `camel-alibaba-common/fc/sms/kms/sls/eventbridge` passes. - The entry survives `PrepareComponentMojo`'s regeneration of the components block. _Claude Code on behalf of davsclaus_ -- 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]
