jira-importer commented on issue #571: URL: https://github.com/apache/maven-deploy-plugin/issues/571#issuecomment-2771552551
**[Jörg Hohwiller](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hohwille)** commented > The request is quite broad. I was asking for four concrete and obvious aspects to write to the log. You can even consider the second as optional. The last two points should be trivial if you know the place in the code that is triggering the HTTP request. Already implementing these two would be a great improvement. I can not see why this should be too "broad"... > As a last resort, one can always enable wire and context logging for the HttpClient. The problem is that coders are facing this problems in external environments such as travis-ci.org or Jenkins. They are technically unable to "enable wire and context logging" and in travis-ci.org this would even expose the password to the public if they could. Further I am proposing a feature that should be enabled by default. So if the problem occurred I get the proper eror details. Isn't it a best practice to give contextual information in case of an error? Why not for maven? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
