Community
Participate
Working Groups
Build Identifier: I20091210-1301 Exception class names in the Console view seem to be underlined not based on the Java class name syntax, but rather on a *Exception like pattern. For example the following is underlined: <longDescription>Exception Obviously this is not a legal class name. Reproducible: Always Steps to Reproduce: Have a Java program print out the string "<longDescription>Exception"
We use the following regular expression to locate exception names in console output. Not sure if this can be improved. We don't resolve the exception to a type unless someone clicks on it - it would be too expensive to resolve them on the fly. "\w[^\(\s]+Exception[\s|:]"
I think this works better: "[a-zA-Z_$][a-zA-Z_$0-9\.]+(Exception|Error)[\s|:]" or even: "[a-zA-Z_$][a-zA-Z_$0-9\.]+(Exception|Error|Throwable)[\s|:]" if you want to catch some oddly named ones.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
Sarika, please check whether this is still an issue.
I can reproduce the problem with I20191120-1800. We still use the same regex as mentioned in comment#1
