Bug 117515 - [Commands] Empty folders not fetched when pruning is off
Summary: [Commands] Empty folders not fetched when pruning is off
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P5 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2005-11-22 11:10 EST by Bruce CLA
Modified: 2019-09-06 16:03 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bruce CLA 2005-11-22 11:10:09 EST 
This was reproduced on Eclipse 3.1. 

Prune empty directory is NOT selected. 

1) PERRY, B.:21Nov2005:
We are using Eclipse 3.0. I created a new folder
"xml\new" in our project.  The folder is currently empty.  I committed this new
empty folder to CVS (and discovered bug 117508 in the process).  

Now, when a second user does a "Team-->Synchronize
with Repository...", the new folder does not appear in the synchronize results. 
The only way we could find to bring this new empty folder into the navigator
workspace was to do a checkout of the entire project from CVS.
Comment 1 Bruce CLA 2006-10-04 11:21:15 EDT 
What is the status of this? 

In 3.2.1, "Replace with latest" brings the new empty folder into the navigator view if you turn of "Prune empty directories". Checking out the project only works in the HEAD branch.
Comment 2 Michael Valenta CLA 2006-10-04 11:30:54 EDT 
We do not plan on addressing this issue in 3.3 but patches will be accepted.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:03:34 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.