Skip to content

Update maven2 mirror repository url order - #352

Merged
reta merged 1 commit into
opensearch-project:mainfrom
peterzhuamazon:maven2-mirror-reorder
Jun 30, 2026
Merged

Update maven2 mirror repository url order#352
reta merged 1 commit into
opensearch-project:mainfrom
peterzhuamazon:maven2-mirror-reorder

Conversation

@peterzhuamazon

@peterzhuamazon peterzhuamazon commented Jun 30, 2026

Copy link
Copy Markdown
Member

Description

Update maven2 mirror repository url order

Issues Resolved

opensearch-project/opensearch-build#6278

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@github-actions

github-actions Bot commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

PR Code Analyzer ❗

AI-powered 'Code-Diff-Analyzer' found issues on commit 4b566da.

PathLineSeverityDescription
bwc-test/build.gradle53highRepository resolution order changed in buildscript block: 'https://ci.opensearch.org/ci/dbc/snapshots/maven/' moved to after mavenCentral(). Per mandatory rule, all package registry/repository configuration changes must be flagged. The reordering changes which repository is queried first for artifact resolution, which can affect which artifact version is ultimately downloaded. Maintainers should verify this reordering is intentional and that no artifacts will now resolve differently.
bwc-test/build.gradle66highRepository resolution order changed in main repositories block: 'https://ci.opensearch.org/ci/dbc/snapshots/maven/' moved to after mavenCentral(). Per mandatory rule, all package registry/repository configuration changes must be flagged. Same concern as the buildscript block — dependency resolution precedence is altered, and maintainers must verify no artifacts will resolve to unexpected versions as a result.

The table above displays the top 10 most important findings.

Total: 2 | Critical: 0 | High: 2 | Medium: 0 | Low: 0


Pull Requests Author(s): Please update your Pull Request according to the report above.

Repository Maintainer(s): You can bypass diff analyzer by adding label skip-diff-analyzer after reviewing the changes carefully, then re-run failed actions. To re-enable the analyzer, remove the label, then re-run all actions.


⚠️ Note: The Code-Diff-Analyzer helps protect against potentially harmful code patterns. Please ensure you have thoroughly reviewed the changes beforehand.

Thanks.

@peterzhuamazon peterzhuamazon added enhancement New feature or request v3.8.0 Issues and PRs related to version v3.8.0 release labels Jun 30, 2026
@peterzhuamazon
peterzhuamazon force-pushed the maven2-mirror-reorder branch from edbf586 to 4b566da Compare June 30, 2026 19:54
@peterzhuamazon peterzhuamazon added the skip-diff-analyzer Maintainer to skip code-diff-analyzer check, after reviewing issues in AI analysis. label Jun 30, 2026
@peterzhuamazon
peterzhuamazon force-pushed the maven2-mirror-reorder branch from 87fcf2c to b71d19a Compare June 30, 2026 20:03
Signed-off-by: Peter Zhu <zhujiaxi@amazon.com>
@peterzhuamazon
peterzhuamazon force-pushed the maven2-mirror-reorder branch from b71d19a to d13e30e Compare June 30, 2026 20:05
@reta
reta merged commit 8abc15a into opensearch-project:main Jun 30, 2026
16 checks passed
@github-project-automation github-project-automation Bot moved this from 👀 In Review to ✅ Done in Engineering Effectiveness Board Jun 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request release skip-diff-analyzer Maintainer to skip code-diff-analyzer check, after reviewing issues in AI analysis. v3.8.0 Issues and PRs related to version v3.8.0

Projects

Status: ✅ Done

Development

Successfully merging this pull request may close these issues.

2 participants