Skip to content
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

Helm Client: Add SLF4J logging support #86

Closed
Tracked by #69
nathanklick opened this issue Jun 8, 2023 · 1 comment · Fixed by #137
Closed
Tracked by #69

Helm Client: Add SLF4J logging support #86

nathanklick opened this issue Jun 8, 2023 · 1 comment · Fixed by #137
Assignees
Labels
New Feature A new feature, service, or documentation. Major changes that are not backwards compatible. released
Milestone

Comments

@nathanklick
Copy link
Member

nathanklick commented Jun 8, 2023

Description

Add SLF4J API and Log4j2/Logback dependencies to the BOM project. Only require the SLF4J API in production code. Logging implementation should only be in unit test code.

Add appropriately leveled log statements where necessary. Prefer static final class level loggers.

@nathanklick nathanklick self-assigned this Jun 8, 2023
@nathanklick nathanklick moved this to 🏗 In progress in FST Suite Jun 12, 2023
@nathanklick nathanklick added this to the v0.1.0 milestone Jun 21, 2023
@nathanklick nathanklick added the New Feature A new feature, service, or documentation. Major changes that are not backwards compatible. label Jun 26, 2023
@github-project-automation github-project-automation bot moved this from 🏗 In progress to ✅ Done in FST Suite Jul 5, 2023
@swirlds-automation
Copy link
Contributor

🎉 This issue has been resolved in version 0.2.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
New Feature A new feature, service, or documentation. Major changes that are not backwards compatible. released
Projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

3 participants