Skip to content

Comments

Bump logback to 1.3.15#2337

Merged
ihrasko merged 1 commit intoPANTHEONtech:22.xfrom
Tobianas:22.xBump
Sep 2, 2025
Merged

Bump logback to 1.3.15#2337
ihrasko merged 1 commit intoPANTHEONtech:22.xfrom
Tobianas:22.xBump

Conversation

@Tobianas
Copy link
Contributor

Override logback version to 1.3.15

JIRA: LIGHTY-365

(cherry picked from commit 7634f5d)

Override logback version to 1.3.15

JIRA: LIGHTY-365
Signed-off-by: tobias.pobocik <[email protected]>
(cherry picked from commit 7634f5d)
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @Tobianas, I'm Gemini Code Assist1! 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!

This pull request updates the version of the Logback logging library to 1.3.15. This is achieved by explicitly declaring the logback-classic and logback-core dependencies within the lighty-core/dependency-versions/pom.xml file. The change includes a note indicating that this explicit override is temporary, intended to ensure the desired Logback version is used until a higher-level dependency (like OpenDaylight) incorporates a newer version itself.

Highlights

  • Dependency Addition: Explicitly added the logback-classic and logback-core dependencies to the lighty-core/dependency-versions/pom.xml file.
  • Version Update: Set the version for both logback-classic and logback-core to 1.3.15.
  • Temporary Override Note: Included a FIXME comment to indicate that these explicit dependencies are a temporary measure and should be removed once the OpenDaylight (ODL) project updates its own logback version.
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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request overrides the version of logback-classic and logback-core to 1.3.15. This is likely to mitigate a security vulnerability or resolve a version conflict from a transitive dependency. The change is functionally correct. I have provided one suggestion to use the Logback Bill of Materials (BOM) for dependency management. This simplifies the pom.xml and ensures version consistency across all Logback modules, which is a Maven best practice.

@ihrasko ihrasko merged commit 9775fd1 into PANTHEONtech:22.x Sep 2, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants