Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 35825

Summary:	[CVS Core] Rename/Move of projects retains CVS information
Product:	[Eclipse Project] Platform	Reporter:	David J. Orme <daveo>
Component:	Team	Assignee:	Platform-VCM-Inbox <platform-vcm-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3
Version:	2.1
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description David J. Orme

2003-03-28 12:16:05 EST

These instructions are with the CVS team provider

1) Create a project
2) Share the project and commit it
3) Rename the top-level project
4) Commit changes

What happens:

Only the .project file is committed at step 4.

What should happen:

I can think of a couple of choices:

I. Automatically re-import
A) Leave the existing repository project as-is for archival purposes.
B) Automatically re-import the workspace's project into a new CVS (or Team
provider) project.

II. Allow manual re-import
A. Prompt the user about removing the project from team control
B. If the user agrees, remove all CVS directories from the project subtree
C. Mark the project as not being managed any longer by the team tooling
D. Allow the user to manually re-import it under the new project name.

Of these choices, I think I would prefer option (II) because it also implicitly
allows the option to import the code into a different team repository.  Suppose
some open source project currently hosted at SourceForge is accepted into
Eclipse.  The project and packages will likely be renamed.  This would also
allow the project to be imported into Eclipse's CVS without any other manual
intervention required.

Comment 1 Michael Valenta

2003-03-28 14:14:37 EST

This bug is related to bug 24156. However, unlike that bug, we could actually 
do something in this case due to the move delete hook. The only thing I would 
suggest doing is to prompt the user with the options to keep the project 
connected to same remote folder or disconnect from CVS and purge CVS 
information. However, I hesitate to do anything for this one separately from 
bug 24156 because I think the cases are similar enough that they should have 
the same behavior (which they do now).

Comment 2 Michael Valenta

2003-03-28 14:16:53 EST

Changed title from "Renaming project introduces inconsistency between workspace 
and team repository"

Comment 3 Michael Valenta

2005-05-06 17:18:51 EDT

This bug has not been touched for 2 years. Closing as WONTFIX. Please reopen if 
you feel this is still an important issue.