[lucacome]

Potential fix for https://github.com/opentracing-contrib/java-spring-cloud/security/code-scanning/1

To fix this safely without changing project behavior beyond replacing the deprecated repository, update the distributionManagement release repository in pom.xml to a supported canonical host for OpenTracing artifacts (JFrog OSS Artifactory, matching the existing snapshot repository family).

Best single fix in this snippet:

• In pom.xml, within <distributionManagement> (around lines 332–340), replace the <repository> entry that currently uses Bintray:
  • keep the <id> as bintray to minimize credential/profile disruption,
  • replace only the <url> with the JFrog OSS release-local endpoint:
    https://oss.jfrog.org/artifactory/oss-release-local.

No imports/dependencies/methods are needed (XML config only).

Suggested fixes powered by Copilot Autofix. Review carefully before merging.

Summary by CodeRabbit

• Chores
  • Updated the release repository configuration to use the current JFrog Artifactory OSS endpoint instead of the deprecated Bintray service.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 38478365-8ba2-4d14-a346-ce90f72e9677

📥 Commits

Reviewing files that changed from the base of the PR and between 5bd3e6a and d1a8149.

📒 Files selected for processing (1)

• pom.xml

Included review availability: Your plan provides up to 2 included reviews per hour; 0 remain after this review.

---

Walkthrough

The Maven release repository URL changed from the deprecated Bintray endpoint to the JFrog Artifactory OSS release repository.

Changes

Release Repository Configuration

Layer / File(s)	Summary
Update release repository URL pom.xml	The Maven distributionManagement release repository now uses the JFrog Artifactory OSS release repository URL.

Suggested reviewers: single-wolf

Merge Risk: ⚪ Minimal · up to d1a81

This localized configuration change replaces the deprecated release repository endpoint without changing project behavior; no actionable merge-blocking risk remains after normal checks and review.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the code-scanning alert and the JCenter/Bintray repository dependency addressed by the change.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/bintray

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}