Bug 20946 - [ExternalTools] Rename tool file/project breaks tool
Summary: [ExternalTools] Rename tool file/project breaks tool
Status: RESOLVED DUPLICATE of bug 52686
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 2.0   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: 3.0   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted, ui
: 21559 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-06-25 10:24 EDT by Adam Schlegel CLA
Modified: 2004-02-24 19:10 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Schlegel CLA 2002-06-25 10:24:08 EDT
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.
Comment 1 Simon Arsenault CLA 2002-07-15 12:58:51 EDT
*** Bug 21559 has been marked as a duplicate of this bug. ***
Comment 2 Simon Arsenault CLA 2002-09-06 15:26:43 EDT
No plans to add this support at this time.
Comment 3 Darin Wright CLA 2002-11-15 12:06:53 EST
The same issue applies to launch configs (as it does to launch configs for java 
programs too). Nothing planned for 2.1
Comment 4 Darin Swanson CLA 2003-07-18 20:05:12 EDT
Reopening for consideration for 3.0
Comment 5 Darin Swanson CLA 2004-02-24 19:10:13 EST
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 ***