chore: update gradle wrapper

[ttypic]

Summary by CodeRabbit

• New Features

  • Introduced a new build configuration for Android and Java projects using Kotlin DSL.
  • Added structured management for library versions and dependencies through libs.versions.toml.
  • Updated project metadata properties in gradle.properties for better project management.

• Bug Fixes

  • Updated Java Development Kit (JDK) version in workflows to ensure compatibility with the latest Gradle tasks.

• Chores

  • Removed outdated Gradle build files and configurations to streamline project structure.

• Documentation

  • Updated licensing information in gradlew and gradlew.bat scripts.
  • Streamlined instructions for building and uploading the library in CONTRIBUTING.md.

[coderabbitai[bot]]

[!WARNING]

Rate limit exceeded

@ttypic has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 11 minutes and 3 seconds before requesting another review.

:hourglass: How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

:vertical_traffic_light: How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

:inbox_tray: Commits

Files that changed from the base of the PR and between a7e2a2204f75552418a181cd7b104d809dea87b7 and 7d70cd93d2206b838486c2f941ad6b8b9309f702.

Walkthrough

The changes involve updates to build configurations across multiple files for a Java and Android project. Key modifications include the introduction of Kotlin support in the .editorconfig, the addition of JDK setup steps in GitHub Actions workflows, and the transition from Groovy to Kotlin DSL in Gradle build scripts. Several files were deleted, including legacy build configurations, while new files were created to enhance project structure and dependency management. The project now utilizes Gradle version 8.7 and incorporates updated properties for project metadata.

Changes

File(s)	Change Summary
.editorconfig	Updated file type patterns to include Kotlin script files (.kts) for indentation settings.
.github/workflows/*.yml	Added steps to set up JDK 17 using actions/setup-java@v3 in multiple workflow files, modifying the sequence of Gradle commands in check.yml.
android/build.gradle, android/maven.gradle, java/build.gradle, java/maven.gradle, common.gradle, dependencies.gradle	Deleted files containing legacy build configurations for Android and Java projects, including Maven publishing setups.
android/build.gradle.kts, java/build.gradle.kts	New files created for build configurations using Kotlin DSL, specifying SDK versions, dependencies, and build settings.
android/src/main/AndroidManifest.xml	Removed package attribute from the <manifest> tag.
build.gradle	Deleted file containing Gradle build configuration for Nexus repository staging.
build.gradle.kts	New file created for top-level Gradle configuration using Kotlin DSL, applying common repository settings.
gradle.properties	Updated with new properties related to project metadata, including group ID, version, and licensing information.
gradle/libs.versions.toml	New file introduced for managing library versions and dependencies in a structured format.
gradle/wrapper/gradle-wrapper.properties	Updated distributionUrl to point to Gradle version 8.7.
gradlew, gradlew.bat	Modified scripts to include licensing information, update JVM options, and streamline execution flow.
settings.gradle, settings.gradle.kts	Removed legacy settings file and introduced a new file to specify project name and include subprojects for multi-module builds.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant GitHub Actions
    participant Gradle
    participant JDK

    User->>GitHub Actions: Trigger Build
    GitHub Actions->>JDK: Set up JDK 17
    JDK-->>GitHub Actions: JDK Ready
    GitHub Actions->>Gradle: Execute Gradle Tasks
    Gradle-->>GitHub Actions: Build Output
    GitHub Actions-->>User: Build Complete

🐇 In the meadow, changes bloom,
New scripts dance, dispelling gloom.
With Kotlin's grace and JDK's might,
Our project hops to new heights!
Dependencies neatly aligned,
A joyful leap, our work refined! 🌼

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

:heart: Share

• X
• Mastodon
• Reddit
• LinkedIn

:placard: 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 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.

[sacOO7]

Overall looks good. Few points to be added

1. Make sure new build scripts work as expected, run all tasks under CONTRIBUTING.md
2. Update newly/updated added gradle tasks under CONTRIBUTING.md( if needed )
3. Ably-java lint/lint-format task is missing, will be great if we can add it.