Update Maven Central badge in README

[yuokada]

Overview

• Updated Maven Central badge to use Shields.io and link to Search Maven, replacing the previous Herokuapp badge and Maven Central link.

[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 enhancing the project's documentation by updating the Maven Central badge in the README. The change replaces an older badge service with Shields.io, providing a more robust and widely used solution for displaying project status, and ensures that the associated link directs users to the official Search Maven platform. This improves the reliability and accuracy of the project's external links.

Highlights

• Maven Central Badge Update: The Maven Central badge in the README has been updated to use Shields.io for its image source and now links directly to Search Maven for artifact details.

🧠 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.

Changelog

• README.md
  • Updated the Maven Central badge to use Shields.io.
  • Changed the Maven Central badge's link to point to Search Maven.

Activity

• No specific activity has been recorded for this pull request yet.

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 the Maven Central badge in the README to use a more reliable service, which is a good improvement. I have one suggestion to make the badge's link more useful for users by pointing to all project artifacts instead of just the core module, which would improve discoverability given the multi-module nature of this project.

_{Note: Security Review has been skipped due to the limited scope of the PR.}

[gemini-code-assist]

The link for the Maven Central badge points to the fluency-core artifact. Since this repository contains multiple publishable modules (e.g., fluency-fluentd, fluency-aws-s3), it would be more helpful for users if the badge linked to a search for all artifacts in the group. This would allow them to easily discover all available modules.

Suggested change

	[](https://search.maven.org/artifact/org.komamitsu/fluency-core)
	[](https://search.maven.org/search?q=g:org.komamitsu)