Bug 289337 - Introduce API for moving projects with IProject specifying target location
Summary: Introduce API for moving projects with IProject specifying target location
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-14 07:46 EDT by Pawel Pogorzelski CLA
Modified: 2019-09-06 16:16 EDT (History)
2 users (show)

See Also:

Attachments
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 Pawel Pogorzelski CLA 2009-09-14 07:46:47 EDT 
As of Eclipse 3.5 IProject.move(...) take IProjectDescription as a parameter specifying target location. As a result during the operation .project file is updated with the new name.

This bug is to investigate new API for moving projects with IProject as an argument. This way project description could be separated from its location. Such a characteristic could be important in context of e4 flexible resources effort.
Comment 1 John Arthorne CLA 2009-09-14 08:45:59 EDT 
Is this to handle the case where the name in .project doesn't match IProject.getName()?
Comment 2 Pawel Pogorzelski CLA 2009-09-14 08:54:24 EDT 
Sample use case of the new API is mentioned in Bug 77637, comment 4.
Comment 3 John Arthorne CLA 2009-09-14 09:11:21 EDT 
Hopefully this could be handled by adding a new flag to IResource#move(IProjectDescription, int, IProgressMonitor) instead of adding a new method...
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:16:30 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.