Bug 191886 - Create Ant Move refactoring participant
Summary: Create Ant Move refactoring participant
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 3.3   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-11 01:55 EDT by Brock Janiczak CLA
Modified: 2019-09-06 15:34 EDT (History)
0 users

See Also:

Attachments
patch to org.eclipse.ant.ui (7.64 KB, patch)
2007-06-11 01:58 EDT, Brock Janiczak CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Brock Janiczak CLA 2007-06-11 01:55:57 EDT 
Version: 3.3.0
Build id: I20070525-1350

Currently when you move an ant build file within or between projects any launch configurations linked to the script will still point to the old location.

1. Create a new build.xml file
2. Launch the script
3. move the file into another project or another directory
4. attempt to run the old launch configuration.  It will complain about the file location not existing.

The attached patch adds a move participant that will attempt to keep the launch configurations in sync with the location of the build file.
Comment 1 Brock Janiczak CLA 2007-06-11 01:58:06 EDT 
Created attachment 70804 [details]
patch to org.eclipse.ant.ui

Adds basic move support for and launch configurations.

The implementation could be cleaned up and NLS keys haven't been done.
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:34:51 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.