-
Notifications
You must be signed in to change notification settings - Fork 2
chore: rename sslcontext-kickstart to ayza and bump it #293
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
also make sure that we have a dependency on `bcprov-jdk18on` since we use this provider in our code
There was a problem hiding this 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 toayza
across the project'spom.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 rootpom.xml
(underdependencyManagement
) andsdk/pom.xml
(as a direct dependency) to ensure its availability for cryptographic operations. - Version Property Updates: New version properties for
bouncycastle
(1.82
) andayza
(10.0.0
) have been introduced in the rootpom.xml
for centralized management, and thebcpkix-jdk18on
dependency insdk/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
-
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. ↩
There was a problem hiding this 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.
|
also make sure that we have a dependency on
bcprov-jdk18on
since we use this provider in our codetakes over this pull from the library author #291