Community
Participate
Working Groups
Until M3, external tools have their own console view (log console view). Now (I20021203) that external tools produce output to the Debug plug-in's console view, it would be great if there were a preference for making the external tool builders run quietly (in a per builder basis).
Consider for 2.1 (time permitting).
you can specify "-quiet" if the external tool is an Ant build.
We could add a check box to the main tab to indicate if output should be captured. The default setting should be to capture output.
Do you really want to have to configure this for each builder? A single "Show console when external tools builders have output" preference would be more consistent with the way the console is managed elsewhere.
I would say that external tools have a very heterogeneous nature, and users would maybe want to be aware of when and how some tools are running, but there are some tools whose results they are not interested on. This is not the case with other console clients, so I believe you don't need to be consistent with them.
For now, I'm releasing a single option that will be available on the external tools preference page. The request to support configuring the console display on a per-configuration basis is valid, but if we do it we should do it for all config types - java, external tools, etc. In fact, we should consider defining the attribute in debug core and putting the UI in the Common tab. Filed Bug 30634 for this request.
Dah. It turns out that the code for determining if the console should be opened is contained in the debug console itself. The way the code is currently structured, there's no way for us to supercede the existing "show console when..." preferences. Bug 29271 requests something that we *can* do, however - We can provide an option on a per-config basis to not capture the output at all. I think this should give you the behavior that you want.