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

Clean up instances of e.printStackTrace in the rest of Sakai

    Details

    • Type: Task
    • Status: RESOLVED
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 12.0, 19.0
    • Component/s: Portal
    • Labels:
    • 12 status:
      Resolved

      Description

      Related to SAM-3032

      There are hundreds instances of e.printStackTrace in the catch code of 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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  jcebellan Jose Cebellán (Entornos de Formación)
                  Reporter:
                  jonespm Matthew Jones
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Git Source Code