Bug 263671 - Project Cloning and Relocation (migration)
Summary: Project Cloning and Relocation (migration)
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.5   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Martin Oberhuber CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 301563 303751
Blocks:
  Show dependency tree
 
Reported: 2009-02-04 12:59 EST by John Pruitt CLA
Modified: 2019-09-06 16:13 EDT (History)
6 users (show)

See Also:


Attachments
patch to demonstrate capability (162.73 KB, patch)
2009-02-04 12:59 EST, John Pruitt CLA
no flags Details | Diff
document to describe the migration capability (32.09 KB, application/pdf)
2009-02-04 13:01 EST, John Pruitt CLA
no flags Details
update to patch demonstrating the capability (162.77 KB, patch)
2009-02-23 16:21 EST, John Pruitt CLA
no flags Details | Diff
update to patch, fixes a bug (162.47 KB, patch)
2009-03-24 17:37 EDT, John Pruitt CLA
no flags Details | Diff
update to patch, fixes another bug (170.18 KB, patch)
2009-12-11 12:56 EST, Francis Lynch CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description John Pruitt CLA 2009-02-04 12:59:05 EST
Created attachment 124702 [details]
patch to demonstrate capability

This is an enhancement for a Project Migration Capability. This is described in more detail in the attached document. Basically it is a variation of a project import. The use case is that there is a reference project someplace. A developer has their own project directory with exactly the same source files as the reference project. The project migration allows key files to be copied from the reference project to the developer project and then import the project into the current workspace. The key files can include source browsing indexes so that the developer is up and running without having to spend time regenerating the index. The key files also include Resource Refresh information so that the imported project does not have to spend time poking the file system in order to learn that the developer files are exactly the same as the reference files. The date/time information from the reference files is captured and used at the time of the import in order to quickly get the new project current.

This involves an extension point to allow a project type (like CDT) to specify and generate key files that should be part of the migration.

A patch is included that demonstrates the capability. A CDT patch is included in https://bugs.eclipse.org/259280 which is dependent on this bug.

The patch includes a public API, an extension point, and 2 wizards to perform the preparation for the migration (an export) and the migration itself (an import)
Comment 1 John Pruitt CLA 2009-02-04 13:01:36 EST
Created attachment 124705 [details]
document to describe the migration capability

adding document that describes the migration capability and its usefulness
Comment 2 John Pruitt CLA 2009-02-23 16:21:32 EST
Created attachment 126502 [details]
update to patch demonstrating the capability

Update to patch to demonstrate the capability. Changes the migration API so that the source project name is not a required input.
Comment 3 John Pruitt CLA 2009-03-24 17:37:14 EDT
Created attachment 129765 [details]
update to patch, fixes a bug

Fixes a bug relating to which files are extracted from the exported zip file. It was supposed to be extracting all non-zero length files but it was only doing one of them.
Comment 4 Francis Lynch CLA 2009-12-11 12:56:01 EST
Created attachment 154321 [details]
update to patch, fixes another bug

Fixes an infinite recursion when collecting file snapshot information that occurred because recursive symbolic links were not being detected. I wasn't allowed to mark the previous patch as obsolete (I think because it was added by John Pruitt) but this patch should definitely be used instead of that one.
Comment 5 Martin Oberhuber CLA 2010-02-02 13:06:26 EST
After due consideration, we would like to contribute a subset of the attached patch in order to support fast project import based on project snapshot data in Eclipse 3.6. I filed bug 301563 to discuss this proposal, please comment such that we can proceed quickly on creating a patch.
Comment 6 Martin Oberhuber CLA 2010-02-04 21:10:51 EST
Due Diligence - clearing this contribution for Eclipse now through, such that we can use it as the base for further development on bug 301563 under supervision of the PMC:
 http://dev.eclipse.org/ipzilla/show_bug.cgi?id=3773
Comment 7 Eclipse Webmaster CLA 2019-09-06 16:13:28 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.