Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 47506

Summary: Eclipse mixs tags when inner CVS directories are used
Product: [Eclipse Project] Platform Reporter: Fernando Colombo <fernacolo>
Component: CVSAssignee: platform-cvs-inbox <platform-cvs-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: 3.0   
Target Milestone: 3.1 M4   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Fernando Colombo CLA 2003-11-26 07:01:47 EST 
For example, if we configure tags for directory /a/b, the same tags are shown
for directories /a/c, /a/d, /a/e/f, etc. The tags seems to be bound to directory
/a, and any directory inside /a will show those tags, even if they aren't
present at that level.

As far as I can see, Eclipse treats only top-level CVS directories as distinct
versioned modules. This isn't good because we have a large tree and many inner
directories can be distinct versioned modules.

The tags to be shown for a given CVS directory should be:
1. All tags that are remembered for that directory; plus
2. All tags that are remembered for any parent directory.

That is, the tags to be shown to directory /a/b must be the tags remembered for
/a/b plus the tags for /a.

And the tags to be shown for /a must be only the tags remembered to /a, since /a
has no parent directory.

If this simple logic was used, then when no tag is remembered for /a, only the
tags remembered for /a/b will be shown for that directory.

Of course, the GUI of CVS Repository view should be changed to allow any inner
CVS directory to be a distinct versioned module.
Comment 1 Jean-Michel Lemieux CLA 2003-12-12 15:30:26 EST 
Agree. We would like to fix-up the whole CVS tag management but I don't know 
if we will have time :(
Comment 2 Jean-Michel Lemieux CLA 2004-06-11 16:50:51 EDT 
Post 3.0
Comment 3 Michael Valenta CLA 2004-11-22 13:56:20 EST 
This has now been fixed. Tags are cached directly with any remote folder they 
are fetched for. The only exception is that operations on local resources will 
used the tags cached with the project.