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.
Start a dev build with a fresh user dir. Create two Ant script, named (using @name in <project>) e.g. "a" and "b". Run "a" (e.g. click Execute on it). The tab "a" is created with the output from "a". Now run "b". The tab "b" is created with the output from "b", but it is not fronted; "a" is still the selected output tab. Run "b" again and it gets fronted. Generally, when creating a new tab, it is not automatically put in front of existing tabs. But if the tab already existed, then it is fronted. In the Ant module there is: io = IOProvider.getDefault().getIO(name, false); io.getOut().reset(); io.select(); // ... io.setFocusTaken(true); io.setErrVisible(false); io.setErrSeparated(false); new PrintStream(...(io.getErr())).println(...); which I believe is correct. It used to work in 3.5 - tabs were fronted.
Reassigning to Marek - Marek, you did the changes to OW for winsys, it's probably more of a winsys thing. Assign it back if you disagree.
It is a thing of OutputTabInner and OutputView impl, not winsys.
I will fix it.
Fixed in main trunk. Mutex.EVENT.readAccess is used instead of plain SwingUtilities.invokeLater to keep code execution order. (In this case tab was opened AFTER call of select() so proper tab was not selected.) Modified: core/output/src/org/netbeans/core/output/OutputTabInner.java r.1.9
Thanks; I will check it soon (use this every day).
closed
moving terminal emulator issues to terminalemulator component. To see the correct version and target milestone of this issue look at Issue Activity table.