Community
Participate
Working Groups
+++ This bug was initially created as a clone of Bug #196035 +++ Some RSE wizard and dialogs log every RSE SystemMessageException to the PDE Errorlog. As bug #142184 and bug #196035 discuss, this is not appropriate since SystemMessageException is typically used for giving users feedback about the outcome of commands. The PDE Errorlog should be reserved for unexpected errors in the system. Reports about rename not working because of a read-only file, or feedback about invalid user input, are not unexpected. They disturb the user when logged to the PDE Errorlog. It is questionable why such exceptions are logged because the user is informed about these exceptions by the means of a dialog or messagebox anyways. One could argue that such exceptions are helpful for problem determination (just tell the customer: "send me the logs"), but then that log should be different from the PDE Errorlog. DaveM proposed "If we look at the code in SystemNewFolderWizard, the non-SystemMEssageExceptions are logged via SystemBasePlugin.logDebugMessage(). I suppose it would make sense to do the same for the SystemMessageExceptions.". But the problem with this is that messages logged with logDebugMessage() will never actually be logged because the logging level Logger.DEBUG cannot be set any more in the UI (Only levels ERROR, WARNING and INFO are now available). Dave D made this change because with level DEBUG it was not possible to use RSE any more since it became too slow. The question is what do we log and where?
I'd like to see this investigated for our F2F Meeting in Chicago (we'll see then what we want to do). Thus tentatively assigning 2.0.1 to ask for investigation by that time.
Bulk update target milestone 2.0.1 -> 3.0
moving to 3.1
