Community
Participate
Working Groups
From the platform-ant-dev mailing list: On the UI front the Ant Console should IMHO be used more like the debug console. By that I mean the current behavior is to throw up a modal dialog and lock the UI while an ant build is executing. For me at least this can lock eclipse for 2+ minutes for a full build. It would be better to kick of the build and have the Ant Console have a red "Terminate" square the same as the debug console to stop the current ant build process. Users still get the ability to cancel and the UI remains responsive through out. Binyan
About the Ant console I agree that it can be useful to have a non modal way of running scripts. Ant runs in the same VM as Eclipse (as opposed to what the debugger does) so it makes sense to lock Eclipse because in that context it is just a long-running operation. Running on a separate VM would lose some Eclipse-specific tasks (e.g. eclipse.refreshLocal) that rely on instances of Eclipse objects. It would be a nice optional feature.
Moving to Platform UI (External Tools) for comment.
Defer until after release 2.0
In the new external tool work, the plan is to use debug's console and process views. You could then run tools in the background (option on the tool itself). Note: new external tool work is not yet released to the head stream and won't for a while yet.
This has not been fixed.
You can now run external tools (and ant scripts) in the background. The Ant wizard will not exist anymore (by M4).
Please verify, Jared.
Verified.