Bug 262747

Summary:

[compare][CVS repositories] additional folders are created during compare

Product:

[Eclipse Project] Platform

Reporter:

Krzysztof Daniel <krzysztof.daniel>

Component:

Team

Assignee:

Platform Team Inbox <platform-team-inbox>

Status:

NEW ---

QA Contact:

Severity:

normal

Priority:

CC:

blazej.kroll

Version:

3.5

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

Attachments:

Description	Flags
New folders created during compare with on two files from diffrent branches	none
The new folders are created just within the CVS repositories view, here are the same branches opened with another instance of Eclipse	none

Description Krzysztof Daniel

2009-01-28 08:38:33 EST

Reproduction steps:
1. create a projects with 2 branches derived from head. Modify a file in those branches (the same file).
2. from CVS repositories view look for one of those branches, find a file, and compare it with another branch.
3. you can notice that in your branch additional folder is generated. It seems to be a parent folder of compared resource.

Comment 1 Blazej Kroll

2009-02-12 06:20:15 EST

Created attachment 125509 [details]
New folders created during compare with on two files from diffrent branches

Comment 2 Blazej Kroll

2009-02-12 06:21:14 EST

Created attachment 125510 [details]
The new folders are created just within the CVS repositories view, here are the same branches opened with another instance of Eclipse

Comment 3 Blazej Kroll

2009-02-12 06:24:14 EST

I checked that the creation of fake folders is just within the CVS Repositories view. These folders are not created in the CVS repository on the server. 
(see attached screenshots)
You can check that by connecting to the CVS server via another Eclipse instance of by copying your CVS connection to clipboard and discarding it and pasting it againg.

Comment 4 Eclipse Webmaster

2019-09-06 15:33:12 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.