Bug 34389

Summary: [DOC] Can't see modules under branches
Product: [Eclipse Project] Platform Reporter: Ritchie Schacher <schacher>
Component: TeamAssignee: Platform-VCM-Inbox <platform-vcm-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 Keywords: faq
Version: 2.1   
Target Milestone: 2.1   
Hardware: PC   
OS: Windows 2000   
Whiteboard:

Description Ritchie Schacher CLA 2003-03-10 13:09:15 EST 
There is no way to get modules to appear under my branch.  We have defined our 
module in the "modules" file of CVSROOT.  We use it as a convienient way to 
load a set of projects from the repo easily, because our repo contains 
literally hundreds of projects.

See the newsgroup thread '2.1 rc1 [cvs] What happened to "show modules"'.
Comment 1 Michael Valenta CLA 2003-03-10 14:00:35 EST 
Performing the following steps to have your module appear under a branch or 
version:

1) Expand HEAD
2) Select the module
3) Choose "Configure Branches and Versions" from the context menu
4) Select a file in the upper left hand pane (expand folders as needed to find 
an appropriate file). The tags should appear in the upper right hand pane.
5) Choose "Add Checked Tags"
6) Optionally choose "Add selected Files" to add the selected file to the auto-
refresh list. Future "Refresh from Repository" actions will then use that file 
to discover new tags.

Do these steps work for you?
Comment 2 Ritchie Schacher CLA 2003-03-10 14:36:29 EST 
yes, it worked.  It took me a few minutes to find a project that had files in 
the HEAD stream; the reason it didn't work before is I didn't search hard 
enough.

I guess I would have expected it to find a .project or .classpath file under 
any project and find all the tags.  Is this what should happen if "configure 
branches and versions" was enabled when selecting the module under "Versions"?
Comment 3 Michael Valenta CLA 2003-03-14 16:19:06 EST 
The action for this bug is to document this workflow. Other bugs will be used 
to track how to improve the workflow in the future (see bug 34413).
Comment 4 Michael Valenta CLA 2003-03-18 09:00:50 EST 
The doc has been updated