Backport to branch(3) : Bump the dependencies group across 1 directory with 10 updates

[feeblefakie]

This is an automated backport of the following:

• Original PR: Bump the dependencies group across 1 directory with 10 updates #204
• Backported commit: 0e07c4c

Please merge this PR after all checks have passed.

[gemini-code-assist]

Summary of Changes

Hello @feeblefakie, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

I have reviewed this pull request and determined it is an automated backport aimed at synchronizing dependency versions on branch(3) with recent updates from the main development branch. It primarily focuses on upgrading various library versions to ensure the project benefits from the latest features, bug fixes, and security patches.

Highlights

• Dependency Backport: I've identified that this PR is an automated backport of dependency version bumps to branch(3), originating from scalar-labs/scalardl/pull/204.
• Specific Dependency Updates: My analysis of build.gradle shows updates for log4j, jackson, scalarDb, junit, junitPlatform, and commonsText.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request is an automated backport that updates several dependencies to their newer patch or minor versions. The changes are straightforward and seem to be routine maintenance. My review includes one suggestion to improve the maintainability of the JUnit dependency management by using a Bill of Materials (BOM), which would make future updates safer and simpler.

[gemini-code-assist]

Maintainability: Consolidate JUnit versions with a BOM

Using separate properties junitVersion and junitPlatformVersion for different components of the same framework can be error-prone, as they might accidentally go out of sync in future updates, leading to potential build failures or runtime issues.

To improve maintainability and ensure all JUnit 5 modules are compatible, I recommend using the JUnit 5 Bill of Materials (BOM). This allows managing all JUnit-related dependency versions with a single property.

You could replace these two properties with a single junitBomVersion and then import the BOM in your subprojects. For example:

// In a subproject's build.gradle
dependencies {
    // Import the BOM (Bill of Materials)
    testImplementation platform("org.junit:junit-bom:${junitBomVersion}")

    // Now, you can declare JUnit dependencies without a version
    testImplementation 'org.junit.jupiter:junit-jupiter-api'
    testImplementation 'org.junit.jupiter:junit-jupiter-params'
}

This change would centralize version control for JUnit, making dependency management simpler and more robust.