publish release and develop changes. Updates logback configuration #3
Conversation
| @@ -184,3 +185,30 @@ project.afterEvaluate { | |||
| } | |||
| } | |||
| } | |||
|
|
|||
| tasks.register("publishVersion") { | |||
There was a problem hiding this comment.
What is the task actually doing? Could it be that the task logic is missing?
There was a problem hiding this comment.
It triggers the MavenPublication "bootJava" (see usage in workflows/publish.yml). But yeah it's not really obvious that the "dependsOn" trigger that one
There was a problem hiding this comment.
What is the rational behind logging JSON encoded logs to stdout and pipe separated logs to a file? Would it not be better to use the same human friendly pipe separated format for both appenders and rather document how to use a custom logback.xml with the client with an example of the JSON encoder?
There was a problem hiding this comment.
I assume that the stdout is used to be processed by another service (like Azure Application Insights or Splunk Universal Forwarder) and therefore the JSON encoding would be the preferred way. I wouldn't know another reason outside of development that would prefer human friendly readable stdout logs
publish release and develop changes. Updates logback configuration
No description provided.