Remove jcenter() as it's sunsetting

[tuancoltech]

Remove jcenter() as it's sunsetting.

[coderabbitai]

Walkthrough

This pull request updates the repository configuration in the build.gradle file. It removes the jcenter() repository from both the buildscript and allprojects sections and adds the mavenCentral() repository to the allprojects section to ensure proper dependency resolution. The overall structure of the build script remains unchanged besides these repository modifications.

Changes

File	Change Summary
build.gradle	Removed jcenter() from buildscript and allprojects sections; added mavenCentral() to the allprojects section

Suggested reviewers

• jo-elimu

Poem

I'm a hopping rabbit with a coding flair,
Skipping old repos into the fresh spring air.
jcenter has hopped away, mavenCentral's here to play,
Dependencies now dance in a bright, updated array.
Carrots and commits, let's celebrate the day!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5ca2fd8 and bc3fc33.

📒 Files selected for processing (1)

• build.gradle (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (5)

• GitHub Check: build (windows-latest, 21)
• GitHub Check: build (macos-latest, 21)
• GitHub Check: build (macos-latest, 17)
• GitHub Check: build (windows-latest, 17)
• GitHub Check: build (ubuntu-latest, 21)

🔇 Additional comments (2)

build.gradle (2)

21-29: Repository Update: Removal of jcenter() and Addition of mavenCentral()

The allprojects repository block correctly removes the deprecated jcenter() and introduces mavenCentral(). This update ensures that dependency resolution continues smoothly using a maintained repository. Please verify that all dependencies previously available via jcenter are present on mavenCentral.

---

3-9: Buildscript Block Verification

The buildscript block remains unaffected by the sunsetting of jcenter(), as it already uses google() and a Maven repository for plugins. No further action is needed here.

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 10.08%. Comparing base (5ca2fd8) to head (bc3fc33).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##               main      #65   +/-   ##
=========================================
  Coverage     10.08%   10.08%           
  Complexity        9        9           
=========================================
  Files            10       10           
  Lines           228      228           
  Branches         42       42           
=========================================
  Hits             23       23           
  Misses          204      204           
  Partials          1        1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.