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.
Hello, Generic text files could be scanned for class names. For example, Maven Cargo plugin produces a log with name TestSuite.txt, which contains log from testng output, sometimes full of exception stack traces: ------------------------------------------------------------------------------- Test set: TestSuite ------------------------------------------------------------------------------- Tests run: 18, Failures: 12, Errors: 0, Skipped: 0, Time elapsed: 38.688 sec <<< FAILURE! testCreateDatasourceMissingRequiredValues(com.somecompany.as4.DatasourceTest) Time elapsed: 2.596 sec <<< FAILURE! junit.framework.AssertionFailedError: Form input for property query-timeout not found. at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertNotNull(Assert.java:220) ... So this output could be parsed and hyperlinked as other log outputs. If scanning a file is too expensive, let user scan any file for class names and stack traces through clicking such action in a context menu of the editor. No doubt this would make developer's life easier. Thanks for considering.
I've noticed that there's an experimental plugin called Stack Analyzer in the beta repository.
(In reply to comment #1) > I've noticed that there's an experimental plugin called Stack Analyzer in the > beta repository. The stack analyzer is now part of 6.9 IDE release, see Window -> Other -> Analyze Stack.
Great! Just yesterday I needed this again, and found that Stack Analyzer was not available in the plugins tab anymore... so this is why. Good news :) Going to try. Diky, skvela prace.
This issue is obsolete. (In reply to comment #2) > The stack analyzer is now part of 6.9 IDE release, see Window -> Other -> > Analyze Stack. "Analyze Stack" is already included.