[22.x] Bump to latest odlparent versions

[Tobianas]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello, 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!

This pull request focuses on bumping the versions of various dependencies and Maven plugins used in the lighty project. The updates span across core modules, applications, and examples, ensuring the project utilizes the latest available and compatible versions of its dependencies and build tools.

Highlights

• Dependency Updates: This PR updates multiple dependencies, including odlparent, aaa-artifacts, controller-artifacts, infrautils-artifacts, mdsal-artifacts, yangtools-artifacts, and junit-bom in the dependency-versions/pom.xml file.
• Plugin Updates: The PR also updates versions of several Maven plugins across different pom.xml files, such as maven-antrun-plugin, maven-enforcer-plugin, maven-compiler-plugin, maven-failsafe-plugin, maven-surefire-plugin, jacoco-maven-plugin, maven-javadoc-plugin, and checkstyle.
• Parent POM Update: The lighty-parent/pom.xml file has been updated to use newer versions of several maven plugins and dependencies.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Activity

• Tobianas authored the pull request.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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. ↩

[gemini-code-assist]

Code Review

This pull request updates multiple Maven dependencies across several pom.xml files. The majority of these are patch or minor version bumps, which should be low-risk. However, the checkstyle dependency is being upgraded from version 11.0.1 to 12.1.2. This is a major version change that could introduce breaking changes to the static analysis rules. It is important to verify that the project still builds successfully and that any new or modified checks are appropriate for the codebase.

[gemini-code-assist]

Upgrading Checkstyle across a major version (11.x to 12.x) can introduce breaking changes. This might include new default rules, changes in rule behavior, or removal of properties, which could cause build failures. Please ensure that the project's continuous integration build passes with this change and consider reviewing the Checkstyle release notes to be aware of any significant updates that might affect code quality standards in this project.