Summary: | [ExternalTools] Should be able to run external tools asynchronously | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Matthew Conway <matt> |
Component: | Ant | Assignee: | Ryan Cooper <ryan_cooper> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | major | ||
Priority: | P2 | CC: | Adam_Schlegel, csmclaren, kehn, simon_arsenault |
Version: | 2.0 | Keywords: | ui |
Target Milestone: | 2.0.1 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Matthew Conway
2002-05-22 18:20:35 EDT
moving to Platform-UI Supporting this would be very nice, but it is not a stop-ship problem. *** Bug 19460 has been marked as a duplicate of this bug. *** Running an external tool like Notepad should not block the UI, and does not need a progress monitor. *** Bug 19207 has been marked as a duplicate of this bug. *** Post 2.0. Post 2.0. As a workaround, on Windows you can do: - create a new external tool - for its location, use: c:\windows\system32\cmd.exe - for its arguments, use: /C start yourprogram The cmd will exit as soon as it has finished starting yourprogram, unblocking Eclipse. Work around for Linux: - Create a new shell script called tool.sh containing the text #! /bin/sh yourprogram $@ & - Set the appropriate executable bits using the shell and chmod - Create an external tool that runs tool.sh The tool.sh file is necessary since External Tools isn't great at handling spaces on Linux, and doesn't do all the command line parsing that the shell does. To be included in 2.0.1 Fix in 2.0.1 code stream. New bug 22393 was open to port this fix to 2.1 stream. |