Summary: | [ExternalTools] Ant Wizard should not "always" be modal | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Rodrigo Peretti <rodrigo> |
Component: | Ant | Assignee: | Jared Burns <jared_burns> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | Keywords: | ui |
Version: | 2.0 | ||
Target Milestone: | 2.1 M3 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Rodrigo Peretti
2002-04-10 09:48:28 EDT
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. |