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 oct 19] While output window hyperlinking normally works for me, there are some weird circumstances where it does not. For example, run the class core/test/unit/src/org/netbeans/core/lookup/InstanceDataObjectModuleTest.java, rev 1.1 (now deleted). (I use this classpath to run it: /space/src/nb_all/openide/test/unit/src:/space/src/nb_all/core/test/unit/src:/space/src/nb_all/openide/src:/space/src/nb_all/core/src:/space/src/nb_all/openide/netbeans/lib/openide.jar:/space/src/nb_all/core/netbeans/lib/core.jar:/space/src/nb_all/core/netbeans/lib/ext/crimson.jar:/space/src/nb_all/core/netbeans/lib/ext/jh.jar:/space/src/nb_all/core/netbeans/lib/ext/parser.jar:/space/src/nb_all/core/netbeans/lib/ext/regexp.jar:/space/src/nb_all/core/netbeans/lib/ext/terminalemulator.jar:/space/src/nb_all/core/netbeans/lib/ext/xerces.jar:/space/src/nb_all/xtest/lib/junit.jar:/space/src/nb_all/xtest/lib/junit-ext.jar) It has one failing test, testReloadDotInstanceSwitchesLookupByNewClass. This test prints a stack trace when run: There was 1 failure: 1) testReloadDotInstanceSwitchesLookupByNewClass(org.netbeans.core.lookup.InstanceDataObjectModuleTest)junit.framework.AssertionFailedError: Assignable to template class: c=test1.SomeAction a.class=test1.SomeAction at org.netbeans.core.lookup.InstanceDataObjectModuleTest.existsSomeAction(InstanceDataObjectModuleTest.java:116) at org.netbeans.core.lookup.InstanceDataObjectModuleTest.testReloadDotInstanceSwitchesLookupByNewClass(InstanceDataObjectModuleTest.java:173) at org.netbeans.junit.NbTestCase.run(NbTestCase.java:74) at org.netbeans.core.lookup.InstanceDataObjectModuleTest.main(InstanceDataObjectModuleTest.java:45) FAILURES!!! The first stack trace line, in existsSomeAction(), is not hyperlinked. (All relevant sources are mounted, incl. IDOMT.java, and the next line from the same class is hyperlinked.) If the exact same output is printed from an Ant script using <echo>, all lines are correctly hyperlinked. So I think this has something to do with timing of the output, perhaps with intermixing of stdout and stderr.
Still easily reproducible, by the way; seems to be semirandom but common.
Target milestone -> 3.3.1.
Fixed in release33 branch. Above described junit testcase (I was able to reproduce with) now works fine for me.
*** Issue 18250 has been marked as a duplicate of this issue. ***
verified, closed
moving terminal emulator issues to terminalemulator component. To see the correct version and target milestone of this issue look at Issue Activity table.