Bug 117329 - [Modules] Can't check out branch on ampersand module
Summary: [Modules] Can't check out branch on ampersand module
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.1.1   Edit
Hardware: PC Windows 2000
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2005-11-21 11:46 EST by David I CLA
Modified: 2019-09-06 16:06 EDT (History)
2 users (show)

See Also:


Attachments
Patch to fix bug 201336 (1.52 KB, patch)
2007-08-29 11:23 EDT, Darius CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description David I CLA 2005-11-21 11:46:30 EST
The "modules" file in CVS can contain an "ampersand module" as described in:

http://ximbiot.com/cvs/wiki/index.php?title=CVS--Concurrent_Versions_System_v1.12.12.1:_Reference_manual_for_Administrative_files#SEC179

Eclipse lets you select this module, but you can't check out a branch or specific tag using it.
Comment 1 Michael Valenta CLA 2005-11-24 10:44:44 EST
As a workaround, you can check out a branch by checking out from head and then replacing with a branch. I agree that it would be nice to be able to expand the module but interpreting modules on the client is not trivial and we don't have the manpower to so it. Patches will be accpeted.
Comment 2 Peter De Velder CLA 2006-07-20 11:14:27 EDT
FYI as the workaround described above, didn't seem to work for all our ampersand modules (I didn't see the branch name I wanted to select in the "replace with a branch dialog")

Here's how we were able to "checkout" a set of ampersandmodules on a branch : 
1- checkout the ampersand modules on the CVS-trunk first
2- export a team-project-set 
3- edit the team-project set, replacing : 

<project reference="1.0,:pserver:my_cvs_server:/my/cvs/repos,root_module,amper_module"/>

with

<project reference="1.0,:pserver:my_cvs_server:/my/cvs/repos,amper_module,amper_module,branch_name"/>

4- importing the team-project-set (in another workspace)

Looks heavy, but if you have many modules, the exported team-project set is useful, because you can relatively be reused for other branches
Comment 3 Szymon Brandys CLA 2007-08-28 05:27:27 EDT
*** Bug 201336 has been marked as a duplicate of this bug. ***
Comment 4 Darius CLA 2007-08-29 11:23:53 EDT
Created attachment 77262 [details]
Patch to fix bug  201336

This patch fixes the bug reported in 201336, but I haven't tested it against bug 117329.

I added the function getRemoteModuleName() to the CheckoutIntoOperation class.  This function was copied from the CheckoutProjectOperation class.  Looking at the  CheckoutToRemoteFolderOperation class it may suffer the same problem, but I don't know how to test it so I don't know if this would break anything.  If it should also be used there, it may be a better idea to move the getRemoteModuleName() function to the parent class, CheckoutOperation, rather than copying the function in each class as I did.
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:06:54 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.