-
Notifications
You must be signed in to change notification settings - Fork 0
optional logging protocol #5
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
base: main
Are you sure you want to change the base?
Conversation
KaidanTheron
left a comment
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.
As discussed:
- remove default logger
- just pass extended job metadata to logger
KaidanTheron
left a comment
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.
i think we are almost there, I don't think we need to be using the logging protocol anymore though. If everything is tested we can merge this bad boy once you remove the deprecated logging protocol
KaidanTheron
left a comment
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.
Sweet. Merge if everything is tested.
Added an optional logging protocol that provides a default implementation should one not be provided.
Updated the build workflow to use deps-deploy to deploy the project to clojars. In the current workflow, you have to run
clj -T:build build/jar, which generates the jar, then you have to runclj -Spomwhich generates a pom.xml file and finallyclj -T:build build/deploywhich will deploy to clojars provided you have CLOJARS_USERNAME and CLOJARS_PASSWORD as environment variables. Deployment is currently untested.