This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 27652 - Remove Java stack trace highlighting code from OutputTabTerm
Summary: Remove Java stack trace highlighting code from OutputTabTerm
Status: RESOLVED FIXED
Alias: None
Product: cnd
Classification: Unclassified
Component: Terminalemulator (show other bugs)
Version: 3.x
Hardware: All All
: P2 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on: 28190
Blocks: 27643 28297
  Show dependency tree
 
Reported: 2002-09-27 15:58 UTC by David Strupl
Modified: 2008-12-23 08:10 UTC (History)
1 user (show)

See Also:
Issue Type: TASK
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Strupl 2002-09-27 15:58:04 UTC 
Deprecation of org.openide.filesystems.Repository
- FileObject findResource(String) affects : 
  
org.netbeans.core.output.OutputTabTerm.OutTermPane.FileObject
getFileObject(String)

Please check whether this will work after new
projects are integrated
(and repository != classpath).
Comment 1 akemr 2002-10-22 14:55:45 UTC 
It's used to find source class when stack trace is displayed in output
window. If source is found -> OW underlines it's line -> clicking on
it opens editor on appropriated row.

There are two use cases:
1. ErrorManager.notify( Throwable) (core/NotifyException) 
2. Execution - err stream is redirected to OW

I don't know how to solve this, if repository != classpath..

Do you have any idea?
Comment 2 Jesse Glick 2002-10-22 15:41:37 UTC 
Well, you have to either delete this feature, or somehow depend on the
Classpath API. I don't know how to do it cleanly.

For case #2, I would say that JavaProcessExecutor (from Java module)
should be responsible for hyperlinking Java stack traces in its own
output.

For case #1, the fact that Java code is involved is intrinsic to the
fact that NB is implemented in Java. Hyperlinking the stack traces is
really only of interest to NB module developers. Perhaps there can be
some interface in OW code (core) which apisupport could implement and
register to lookup - the impl would know about the Classpath API and
offer to hyperlink lines of output.
Comment 3 akemr 2002-10-23 09:37:12 UTC 
Thanks, Jesse. I agree with your suggestion.

#2: I created task #28190 for Java module.

#1: This feature is really not as important, so I created 
    just P4 ENH #28191 to implement it.

The rest of this task will be cleaning the parseException stuff in
OutputTabTerm (after new projects are integrated)
Comment 4 Marian Mirilovic 2002-12-06 17:14:11 UTC 
reassigne to Tim, new owner of terminal emulator
Comment 5 Jesse Glick 2004-01-07 17:25:20 UTC 
Mine to take care of together with issue #28190.
Comment 6 Jesse Glick 2004-03-16 16:57:27 UTC 
Done in trunk.
Comment 7 Quality Engineering 2008-12-23 08:10:29 UTC 
moving terminal emulator issues to terminalemulator component.
To see the correct version and target milestone of this issue look at Issue
Activity table.