Community
Participate
Working Groups
Sometimes, e.g. in crash logs, I only have class names like org.eclipse.swtbot.swt.finder.widgets.AbstractSWTBot$13 to go by in order to find the problem source. This is not a problem for top-level classes, where I can just open the type by name. It's a lot more difficult to open inner classes this way though. For named inner classes, I can either search by simple name, or if that's to common, use the FQN in dot-notation (e.g. java.util.Map.Entry). java.util.Map$Entry, as usually encountered in logs, does not work. For anonymous classes, this doesn't work at all: neither org.eclipse.swtbot.swt.finder.widgets.AbstractSWTBot.13 nor org.eclipse.swtbot.swt.finder.widgets.AbstractSWTBot$13 gives a match. This makes navigating to these types a real pain. I propose to extend "Open Type" to support - $-notation in addition to dot-notation for nested classes - opening anonymous classes by their FQN (Additionally, I think it would be nice to support qualified names without the package component, as often seen for named inner classes, e.g. "Map.Entry". But that might be worth a separate issue) This might be related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=515081
