Bad class name in --methodlist not handled in same way as bad name from --classlist or --testclass

[bjkeller]

Bad class names are treated differently when they occur in --methodlist input than when they are given using --classlist or --testclass.

When --silently-ignore-bad-class-names is set, a ClassNotFoundException exception that is thrown by a call to Class.forName with one of these exceptions is supposed to be ignored. This currently happens for names from --classlist or --testclass in OperationModel.addClassTypes().
But for --methodlist bad classnames are recognized in SignatureParser.parse() and an exception is thrown regardless of the --silently-ignore-bad-class-names flag.