Community
Participate
Working Groups
From Bug #226262 comment 1: IShellService#launchShell() IShellService#runCommand() IShellService#getHostEnvironment() need to contact the remote side, but have no useful means of returning an error status with message to the user, in case anything goes wrong. All they can do for now, is return an IHostShell object that is not active - but that doesn't include an error message. I propose that all these methods should throw SystemMessageException in order to inform the user when something goes wrong. Currently, we have some ugly exception.printStackTrace() in the Constructor of SshHostShell, for instance; this problem would then go away. This request is a breaking change since SystemMessageException is a checked exception, and clients who call these methods are currently not prepared to handle it.
Created attachment 95432 [details] Patch adding requested throws and fixing Javadoc Attached patch performs the requested API change. Migration Docs: --------------- When the compiler warns about unhandled SystemMessageException while using IShellService, add exception handling to properly handle it. This fix should allow us to properly handle bug 215059.
Patch committed: [api][breaking] IShellService methods should throw SystemMessageException