On 02/22/2013 12:23 PM, Scott Cowan wrote:
I supposed this means when a plugin experiences an unexpected error and logs it as SEVERE, the admin would have to add a logger and reproduce the problem to get the stack trace.
I think plugins are just supposed to use loggers in the jenkins.* namespace to begin with, though I acknowledge that this clashes with the usual package name recommendations for new plugins. I am not sure why WebAppMain.installLogger only registers the jenkins (and hudson) namespace hierarchies, rather than just capturing all log messages in the JVM; maybe to avoid picking up logging from app containers and the like? But then it would be better to capture all log records by default, and skip just those whose source class name can be determined to be part of the container (e.g. defined in a class loader which is an ancestor of that used to load Jenkins.class).
Probably best to file a bug report (and pull request if possible). -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
