Marcono1234 commented on PR #20:
URL: 
https://github.com/apache/maven-jarsigner-plugin/pull/20#issuecomment-2212519982

   @elharo, regarding your comment here and also your [comment on 
JIRA](https://issues.apache.org/jira/browse/MJARSIGNER-76?focusedCommentId=17863556&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17863556):
   > This is yet more unactionable log junk for builds that already have far 
too much of it. 
   
   I don't really agree that it is "unactionable" (nor that is "junk"). As 
mentioned in the issue description on JIRA, the current output does not make it 
clear which files the plugin actually signed. Or what do you mean by 
"unactionable"? Technically all INFO messages from Maven and plugins are 
unactionable because they just inform you what Maven or the plugins are doing, 
without prompting you to change anything (unlike WARNING or ERROR).
   
   And sure, it would be great if Maven printed nearly nothing to the console 
and everything just worked. But in the cases where something does not work, or 
even where the build is successful but the result in unexpected, such output 
can be useful for troubleshooting.
   And you can customize Maven logging to only log WARNING and above.
   
   Or which cases are you thinking of where this output is not useful? Builds 
with dozens of signed files? I would just like to know why you are so strongly 
opposed to this.
   
   As suggested by @lasselindqvist above, would it be acceptable to log this at 
DEBUG level?


-- 
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]

Reply via email to