Bug 136148 - Add an option to "Share with CVS" when doing bulk import
Summary: Add an option to "Share with CVS" when doing bulk import
Status: RESOLVED DUPLICATE of bug 104203
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2006-04-11 13:18 EDT by Adam Hupp CLA
Modified: 2007-06-20 13:56 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Hupp CLA 2006-04-11 13:18:09 EDT
(version 3.2M6)

I removed my .metadata directory and tried to re-import 50 projects back into my workspace.  The import went fine, but it did not recognize that these were CVS checkouts.  I have to individually "Share Project" on each of them.  It would be nice if there was an option to automatically link the projects up with CVS if they have CVS metadata.
Comment 1 Michael Valenta CLA 2006-04-11 13:24:41 EDT
There is a preference for this on the Team>CVS preference page. Can you check to see if it is enabled?
Comment 2 Adam Hupp CLA 2006-04-11 13:48:08 EDT
Yes, it is enabled.
Comment 3 Michael Valenta CLA 2006-04-11 14:00:25 EDT
We will invesigate suring the RC1 test pass.
Comment 4 Adam Hupp CLA 2006-04-11 15:17:37 EDT
More info: I did the import via the "Existing Projects into Workspace" import tool.  I chose a single root directory for the import.  The imported projects are a mix of CVS and non-CVS projects.
Comment 5 Michael Valenta CLA 2006-04-12 10:10:19 EDT
I tireed your scenrio and it worked. I suspect there is a timing issue somewhere. Unfortunately, we won't have time ot track this down in 3.2.
Comment 6 Michael Valenta CLA 2006-08-17 09:15:25 EDT
We do not have the manpower to look at this issue in 3.3.
Comment 7 Michael Valenta CLA 2007-06-20 13:56:51 EDT

*** This bug has been marked as a duplicate of bug 104203 ***