Community
Participate
Working Groups
Build 20020924 1. Create a workspace which is connected to two different CVS repos: :extssh:<yourname>@dev.eclipse.org:/home/eclipse :extssh:<yourname>@zrhcvs1.zrh.oti.com:/home/cvs/eclipse 2. Add one project from each repository: com.oti.zrh.eclipse.tools from zrhcvs1.zrh.oti.com org.eclipse.compare from dev.eclipse.org 3. In the Package Explorer copy the source folder 'src' from com.oti.zrh.eclipse.tools to org.eclipse.compare 4. Repeat 3. 5. Press Yes on the dialog. ==> BAD: the CVS folders are copied along with the source folder! Note: you only see this outside Eclipse 6. In org.eclipse.tools/src open the properties for package com.oti.zrh.eclipse.tools.internal.docTools ==> CVS thinks it still belongs to the zrh repository. This leaves org.eclipse.compare in a total mess making further Team actions totaly unpredictable. NOTE: Same steps work within navigator. Assume the bug is in the hierarchy of JdtCopy action.
we simply call folder.copy(path, false, new SubProgressMonitor(pm, 1)); where folder is the 'src' folder and path is the path to org.eclipse.compare copying or not-copying cvs folders is not under ui control
IResource.copy copies all children if the resource is a folder or project. This includes CVS folders (which are team private members). It would require new API if we wanted to have a #copy which ignored team private resources. Adding Jeem and KM to CC for comment on behaviour of team private resources w.r.t. copy.
This is a known issue and is basically the same as the problem we discussed before with the provider persistent property being copied.
Lowering severity. Assess after 3.0
I'm marking this as a duplicate of a recent request for a repository copy hook, since that is what CVS would need to implement this. *** This bug has been marked as a duplicate of 109166 ***
