|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I'm worried about the drop in the quality of reported bug due to this change.
It seems to me that the number of cases where the stack trace is security sensitive is very small, whereas the stack trace is often very useful in identifying where the problem is and how to work around.
Could this functionality be moved to another plugin that can be installed by security conscious deployments?