Community
Participate
Working Groups
If you copy a file from the head say back into a branch which does not have those files then the files are copied with their cvs connection to the head intact, that in itself is fine. Now if I want to commit these files to the branch I thought I could use the usually file, properties, cvs, disconnect but that option is not there. Also the properties for this file now claim that the file has the tag of the branch whereas the file is not associated with the branch it is associated with the head. Is there a different work flow I should be following to do this kind of action? It is inconvient to go outside of eclipse to the windows file manager and copy the files in b/t branches like this. At minimum I'd like to have the disconnect button back.
What do you mean by "copy a file from HEAD to branch"? Please, could you provide an explicit set of steps to reproduce the problem and stated what behavior you saw and the expected behavior? Also, could you include the Eclipse build you are using?
I am using e3m4. The disconnect button is actually still there I didn't realize it only exists on the directory and not on the individual resources within the directory. Original State ---------------- HEAD project src/dir1/file1.java src/dir1/file2.java Branch project src/hello [ascii] Steps: ========================== 1. Select dir1 in navigator from head project, rc, copy. 2. navigate to src in branch project paste. 3. cvs head info tagging information takes a while to propagate and list them as head resources 4. rc one of the newly copied files and click cvs. 5. notice that the tag listed is branch and not head for this resource. new State ---------------- HEAD project [HEAD] src/dir1/file1.java src/dir1/file2.java Branch project [BRANCH_NAME] src/hello [ascii] src/dir1/file1.java [HEAD] src/dir1/file2.java [HEAD] Ideally I could copy the files wo their cvs tag affliation being copied as well. Hope that makes more sense.
Note that to reproduce this, you may also need to update the branched project before pasting just to ensure that all the remote directories are cached. We have code that will detect copies and purge the CVS folders from them. This detection is not happening properly when pasting over a directory for which a phantom exists. I'll try and have a look to see if a fix is possible. However, given that you can't copy in the file system this way, it is not unreasonable to have the same restriction in Eclipse. Merging is the proper way to move code from one branch to another.
No time to address this in 3.1
*** Bug 198373 has been marked as a duplicate of this bug. ***
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.
