Community
Participate
Working Groups
If you create an External Tool for an Ant script in the workspace, and then move/rename the Ant script using the Workbench, the External Tool is not updated. This causes the tool file to be incorrect, and running the tool to fail. The same behaviour is seen when renaming the tool's project. This is particularly annoying when working with External Tool Builders that run for auto builds. Any time a build is run, the tool fails, and reports it to the user. Tighter integration should be possible. The workbench should have some way of communicating with the External Tools that would allow them to stay in synch.
*** Bug 21559 has been marked as a duplicate of this bug. ***
No plans to add this support at this time.
The same issue applies to launch configs (as it does to launch configs for java programs too). Nothing planned for 2.1
Reopening for consideration for 3.0
Project rename no longer causes a problem for external tools. See bug 37944 for details. Users really should not move external tool launch configurations. The rest of the problem(s) should be covered by bug 52686. *** This bug has been marked as a duplicate of 52686 ***