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.
[current sources] The ant module depends on the Java API, but the ant support can be used also by other products that does not incorporate Java support. So I would suggest to move the Ant&Java somewhere (separate module?) from the base Ant module. In fact, I found that there are two places where the Java API is actually used: 1. org.apache.tools.ant.module.run.AntOutputParser: in this case, I think that parsing the output should be preferably on the module that starts the parsing (for example the LaTeX output is completelly different from the output from Java). 2. org.apache.tools.ant.module.bridge.AntBridge
Yes I would like to fix this too. Re. #1 (stack trace hyperlinking) - I am considering other architectures in light of issue #42525, but it will require some kind of API. As a rule, any output matching <abs-filename>:[:<line>[:<col>[:<end-line>:<end-col>]]] <message> will automatically be hyperlinked. However some tasks are unable to generate properly-formatted error messages, and of course stack traces do not follow this pattern. Re. #2 - this usage can probably be removed, it is not at all important. Just lets user define custom input handler (a very obscure bit of functionality that should probably be dropped, and anyway could be done differently).
Already fixed in ant_loggers_42525 branch.
Fixed.
Seems OK in current sources.