Skip to content

Conversation

mkleene
Copy link
Contributor

@mkleene mkleene commented Sep 18, 2025

also make sure that we have a dependency on bcprov-jdk18on since we use this provider in our code

takes over this pull from the library author #291

also make sure that we have a dependency on `bcprov-jdk18on`
since we use this provider in our code
@mkleene mkleene requested review from a team as code owners September 18, 2025 14:08
Copy link
Contributor

@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 @mkleene, 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 primarily updates the project's dependency configuration. It renames the sslcontext-kickstart library to ayza and ensures that the bcprov-jdk18on Bouncy Castle provider is correctly included, which is essential for the application's cryptographic functionalities. These changes streamline dependency management and align the project with the latest library naming conventions and requirements.

Highlights

  • Dependency Renaming: The sslcontext-kickstart library and its associated modules (sslcontext-kickstart-for-pem, sslcontext-kickstart-for-netty) have been renamed to ayza across the project's pom.xml files, reflecting an upstream change in the library's naming.
  • Bouncy Castle Dependency Addition: The bcprov-jdk18on dependency from the Bouncy Castle Cryptography Library has been explicitly added to both the root pom.xml (under dependencyManagement) and sdk/pom.xml (as a direct dependency) to ensure its availability for cryptographic operations.
  • Version Property Updates: New version properties for bouncycastle (1.82) and ayza (10.0.0) have been introduced in the root pom.xml for centralized management, and the bcpkix-jdk18on dependency in sdk/pom.xml now inherits its version from the parent.
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.

@mkleene mkleene changed the title fix: rename ayza chore: rename sslcontext-kicktart to ayza Sep 18, 2025
Copy link
Contributor

@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 renames the sslcontext-kickstart dependency to ayza and updates its version. It also introduces bouncycastle.version to manage Bouncy Castle dependencies and adds bcprov-jdk18on as a dependency, which is necessary for the cryptographic operations in the SDK. The changes are logical and align with the PR's goal. However, I've found a critical issue with the specified Bouncy Castle version which will break the build. Please see my comment for details.

Copy link

@mkleene mkleene changed the title chore: rename sslcontext-kicktart to ayza chore: rename sslcontext-kickstart to ayza and bump it Sep 18, 2025
@mkleene mkleene merged commit 30a376a into main Sep 18, 2025
12 checks passed
@mkleene mkleene deleted the rename-ayza branch September 18, 2025 14:59
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.

3 participants