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.
Summary: | RuntimeException during Debugger start | ||
---|---|---|---|
Product: | cnd | Reporter: | Jan Lahoda <jlahoda> |
Component: | Terminalemulator | Assignee: | _ tboudreau <tboudreau> |
Status: | VERIFIED INVALID | ||
Severity: | blocker | CC: | jjancura, mkubec |
Priority: | P3 | ||
Version: | 3.x | ||
Hardware: | Sun | ||
OS: | SunOS | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | The RuntimeException thrown. |
Description
Jan Lahoda
2003-11-19 15:20:20 UTC
Created attachment 12222 [details]
The RuntimeException thrown.
This is as designed. It is not actually thrown, just written to the log file to encourage users of SplittedPanel to replace it with JSplitPane. SplittedPanel will soon be moved to openide.deprecated. AFAIK ErrorManager.INFORMATIONAL warnings will be suppressed in release builds. It's meant to be annoying. Well, I maybe missed something, but org.netbeans.core.output.OutputTabInner uses a deprecated class (org.openide.awt.SplittedPanel). I think this is not OK (regardless the exception is printed or not) and should be fixed. Yes, and I own the output window, and I will fix it there. If there is no warning, people will continue using SplittedPanel. This is the same type of warning we give for other things (Jesse's recent asynchronous action changes, for instance). Unless I annotated it wrong and you are seeing a stack trace *dialog*, then this is working *exactly* the way it is supposed to. It is not a bug. Well, I probably did not write it clearly once more. What I was suggesting by this bug was removing this exception from the log by *fixing* OutputTabInner, *not* by commenting out the warning in SplittedPanel (what is the way you understand it). From my point of view, the exception in the log is a problem, and the only clean way to remove it is to fix the OutputTabInner so it does not use the deprecated class. So I supposed you will solve it by using JSplitPane instead of SplittedPanel (please note that I never suggested to remove the warning from the SplittedPanel, in fact I said I think the problem is in OutputTabInner). I cannot understand what is the reason why is the issue invalid. To say it concise: I did not wish you to modify SplittedPanel, but OutputTabInner. Yes, I plan to do that ASAP. FYI, as part of the fix for issue 24824, I have replaced the SplittedPanel in the output window with a JSplitPane. So, no more warnings (at least from the output window). Honza L. , verify your reported issues ASAP after resolution (in the future) ..... , thanks in advance verified moving terminal emulator issues to terminalemulator component. To see the correct version and target milestone of this issue look at Issue Activity table. |