Currently if a client of the output window API wants to display links to the
java sources in stack traces, it has to go through each line, analyze it and
create the link. Having some kind of support for linking the java sources would
prevent duplication of code among different output window clients, which is hard
This requirement goes against the philosophy of Output Window, which is
basically only a fast viewer of possibly very large stream. Output Window does
not know anything about the semantics of the text it displays.
Here is an user opinion to reconsider. It's about usability. JBuilder had this
feature from version 7. Whenever exception stack traces are printed in the
output window, it provides source links if the sources are available in the open
projects. Makes it easier to understand and fix the problem. Isn't a good use
case for enhancement?
krishs: not arguing such a feature is bad, but it ought not be implemented in
the output window itself, but somewhere else.
only the module that writes into the output window is capable of matching the
output to the context and link to the source files. OW doens't know anything
about projects, app servers or anything else that might be necessary for
analyzing the stacktrace.