Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-36475

Clean up instances of e.printStackTrace in Samigo

    Details

    • 12 status:
      Resolved
    • Previous Issue Keys:
      SAM-3032

      Description

      There are over a hundred instances of e.printStackTrace in the catch code of Samigo (and hundreds elsewhere in Sakai). It's recommended not to use this as it's basically the same as System.out.println and can have unpredictable results and considered bad practice since it prints to System.err which could very likely be printed nowhere on tomcat.

      This should really be using the regular log system if the error message warrants it. I'll create a standard SAK and link to this, but there seems to be a lot of these in Samigo that would be nice to catch.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  ncaidin Neal Caidin
                  Reporter:
                  jonespm Matthew Jones
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  6 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Git Source Code