Refactor: replace System.out with SLF4J logging

[guto-alves]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @guto-alves, 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 refactors the logging mechanism within the LoteriasUpdate and ScheduledConsumer classes. It replaces direct console output and stack trace printing with the SLF4J logging facade, enhancing log management, flexibility, and integration with various logging implementations. The change standardizes how messages and errors are reported during the lottery data update and scheduling processes, making the application's behavior easier to monitor and debug.

Highlights

• Logging Refactor: Migrated logging from direct System.out.println and e.printStackTrace() calls to use the SLF4J logging facade in LoteriasUpdate and ScheduledConsumer classes.
• Improved Log Detail: Enhanced log messages to provide more context, including specific lottery names, contest numbers, and attempt counts during update processes.
• Standardized Error Handling: Standardized error logging using logger.error with proper exception handling, replacing generic stack trace printing.

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 is a great step forward, refactoring the application to use SLF4J for logging instead of standard output. This will significantly improve logging capabilities and maintainability. The implementation is mostly well-done, but I've identified a couple of areas in the error logging that could be improved to be more effective for debugging. Specifically, one error log is missing the exception's stack trace, and another logs a misleading value. My suggestions aim to correct these to ensure logs are as helpful as possible.