Eclipse Console - what are the rules that make stack traces clickable?

Question

I log quite a bit of stuff, and have noticed that Eclipse Console makes Java stacktraces clickable. The exception is highlighted (goes to the "Create Breakpoint" dialog box) and the filename + numbers are highlighted too (allows going straight to that line).

I was wondering if I could format my normal log lines so the Eclipse Console would do the same to them. A possible approach could be making them look like stack trace lines, but in order to keep as much information as possible I would like to know the exact rule that Eclipse use to detect these lines, but Eclipse 3.6.2 is rather big so it is a herculean task.

The question is then, what are the rules in play here, and where are they defined?

Edit: The logback pattern layout snippet is %msg \(%file:%line\)%n

AFAIK, when eclipse detects canonical **classnames** and java **filenames** surrounded by `()` (like `(Thread.java:50)`) it automatically makes it clickable. By default. I've seen some plugins make any other files clickable too. — bluefoot, Mar 08 '11 at 13:26
This also works in IntelliJ (for source files actually in the workspace) — Thorbjørn Ravn Andersen, Oct 18 '16 at 17:40

score 9 · Accepted Answer · edited May 23 '17 at 12:03

This snippet may help. It can be placed anywhere in your code and will print a "clickable" line on the eclipse console:

StackTraceElement s = Thread.currentThread().getStackTrace()[1];
System.out.printf("%s.%s(%s:%s)%n", s.getClassName(), s.getMethodName(),
            s.getFileName(), s.getLineNumber());

Update:

This question has an answer, that may include a solution for your problem:

Eclipse console: detect warning and error patterns and make them clickable

Here we go: we have to contribute an implementation of org.eclipse.ui.console.IPatternMatchListenerDelegate through extension point org.eclipse.ui.console.consolePatternMatchListeners.

The contributions that provide hyperlinks for exceptions and line numbers in stack traces are defined in the org.eclipse.jdt.debug.ui plugin, the implementing classes are in the same bundle.

The rules are regular expressions and can be found in the plugin.xml of the contributing plugin.

Thanks for answering. I would still like to see the actual rules, though. — Thorbjørn Ravn Andersen, Mar 08 '11 at 15:34

score 3 · Answer 2 · answered Mar 08 '11 at 13:27

3

If you print (filename:lineNumber), Eclipse will convert it to a link.

Example:

System.out.println("message (Hello.java:2)");

I don't know if there are other rules or where they are defined.

answered Mar 08 '11 at 13:27

dogbane

266,786
75
396
414

user1666456 · Answer 3 · 2018-07-27T07:48:55.823

The question is then, what are the rules in play here, and where are they defined?

The actual regex can be found here: https://github.com/eclipse/eclipse.jdt.debug/blob/e7932c6319b3a96526134940ca57de0576e9607a/org.eclipse.jdt.debug.ui/plugin.xml#L3371

It boils down to something like

\(\w*\.java:\S*\)

i.e. only the parenthesized part is matched. The console then delegates the match to org.eclipse.jdt.debug.ui.JavaConsoleTracker which is an implementation for IPatternMatchListenerDelegate. This creates the respective IHyperlink (JavaStackTraceHyperlink). Only on clicking on the link the actual parsing is done, the whole line is read again to fetch the full package name etc. which is then searched for in the workspace.

In case anybody like me needs to implement this behaviour outside of the Console (e.g. with StyledText):

Match links with some regex, add respective StyleRange (cf. SWT.UNDERLINE_LINK) with the data property set to the link data. On click, search the actual file in the workspace by package/class with:

SearchEngine search = new SearchEngine();
NullProgressMonitor monitor = new NullProgressMonitor();
TypeNameMatchRequestor collector = result -> {
    IPath path = result.getType().getPath();
    //handle result, e.g. open editor
};
search.searchAllTypeNames(fullPackageName, SearchPattern.R_EXACT_MATCH, className, IJavaSearchConstants.TYPE, IJavaSearchConstants.TYPE, SearchEngine.createWorkspaceScope(), collector, IJavaSearchConstants.WAIT_UNTIL_READY_TO_SEARCH, monitor);

score 0 · Answer 4 · answered Feb 18 '16 at 19:15

0

fullyQualifiedClassName.methodName(fileName:lineNumber)

Without fullyQualifiedClassName, Eclipse may choose the wrong file. methodName is required for matching but not used -- it can be anything.

answered Feb 18 '16 at 19:15

NateS

5,751
4
49
59

Eclipse Console - what are the rules that make stack traces clickable?

4 Answers4

Linked