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.
dev build 200202190100 1. Pick a file containing errors 2. Hit COMPILE while in RUNNING-mode 3. Compiler will indicate "compile errors" on top status indicator, however they will not show up in the OUTPUT WINDOW 4. Click on EDITING tab, and errors will show in OUTPUT WINDOW I set this to P2 because I think it's a regression; adjust priority as you see fit.
Strange, I cannot reproduce it at all, so decreasing the priority for now. Could you add more details? - how do you exactly do 2. step (there is no Compile in Running mode normally): using View Explorer or Source Editor? - do you see empty OW (in RUNNING) or no OW at all? - could you try it with sun jdk? Thanks.
Marking as WORKSFORME because not able to reproduce. Feel free to reopen, if it appears again and you can provide more details.
Clarification: the error isn't so much that compiler errors don't show up, rather the problem is that if you have two tabs in the output window: COMPILER OUTPUT and APPLICATION OUTPUT and you compile and get errors, the focus will not automatically shift to COMPILER OUTPUT. This works for all modes, including EDITING MODE. Furthermore, if you're in RUNNING MODE and COMPILER OUTPUT isn't even listed in one of the tabs, not only will the focus not change to the compiler errors, but the tab itself isn't there to switch to. My recommendation: 1. Run a program which works and outputs something to stdout 2. Screw up its source code and try running it again 3. Notice the compiler errors don't show up and the focus doesn't change to the COMPILER ERRORS tab.
Thanks, I found out the problem. Fixed in trunk.
verified 200211070100
Resolved for 3.4.x or earlier, no new info since then -> closing.
moving terminal emulator issues to terminalemulator component. To see the correct version and target milestone of this issue look at Issue Activity table.