Skip to content

branch-4.0: [chore](dep) pin esdk-obs-java-bundle to 3.21.11 to fix version range resolution failure #63278#63283

Merged
morningman merged 1 commit into
branch-4.0from
auto-pick-63278-branch-4.0
May 16, 2026
Merged

branch-4.0: [chore](dep) pin esdk-obs-java-bundle to 3.21.11 to fix version range resolution failure #63278#63283
morningman merged 1 commit into
branch-4.0from
auto-pick-63278-branch-4.0

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

Cherry-picked from #63278

… resolution failure (#63278)

## Problem

The version `[3.21.11,)` in `fe/pom.xml` is a Maven version range, which
requires Maven to download `maven-metadata.xml` from **every configured
repository** and merge the results before selecting a version.

The Huawei OBS Maven repository
(`https://repo.huaweicloud.com/repository/maven/huaweicloudsdk/`) does
not carry this artifact at all (returns 404 for its metadata) or is not
stable. This causes `maven-remote-resources-plugin` to fail the entire
range resolution and report:

```
No versions are present in the repository for the artifact with a range [3.21.11,)
  com.huaweicloud:esdk-obs-java-bundle:jar:null
```

## Fix

Pin the version to the specific minimum `3.21.11`, which is available on
Maven Central (and its mirrors such as aliyunmaven).

With a fixed version, Maven resolves the artifact by trying repositories
one by one and succeeds as soon as any working repository (e.g.
aliyunmaven) responds — it no longer depends on the unstable Huawei OBS
repository for range resolution.

## Verification

`3.21.11` is confirmed present on Maven Central:
```
https://repo1.maven.org/maven2/com/huaweicloud/esdk-obs-java-bundle/3.21.11/
```

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
@hello-stephen
Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@hello-stephen
Copy link
Copy Markdown
Contributor

run buildall

@hello-stephen
Copy link
Copy Markdown
Contributor

skip buildall

@hello-stephen
Copy link
Copy Markdown
Contributor

FE UT Coverage Report

Increment line coverage `` 🎉
Increment coverage report
Complete coverage report

@morningman morningman merged commit f9a04f5 into branch-4.0 May 16, 2026
31 of 34 checks passed
@github-actions github-actions Bot deleted the auto-pick-63278-branch-4.0 branch May 16, 2026 01:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants