Bug 39341 - [CVS UI] Allow for configuration of pruning directories on project check out.
Summary: [CVS UI] Allow for configuration of pruning directories on project check out.
Status: RESOLVED DUPLICATE of bug 43112
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P4 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2003-06-25 15:52 EDT by Marcus Malcom CLA
Modified: 2004-05-22 21:28 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus Malcom CLA 2003-06-25 15:52:09 EDT
CVS Perspective à CVS Repositories

Right click on a folder
	à Check out as Project
	à Check out as …
	à Check out into …

It would be nice to provide a configuration option whether or not to prune empty
directories on the above ways to check out a project. This could be a setting
under Window à Presences : Team à CVS, etc. Or this could be a check-box on the
corresponding pop-up window.

The reason for this, is that for day-to-day activities it is very nice to have
the “Prune empty directories” option set. However, initially checking out a
project it is beneficial to allow a developer to distinguish. This stems from
creating a default project structure (not in Eclipse – via scripts on the server
where the CVS repository is located). This default project structure will
contain empty directories; however, these are essential to the project. So if
prune is on, the project will not be built correctly. Another way to put it, the
project would not be checked out properly.
Comment 1 Michael R Head CLA 2003-06-25 15:58:49 EDT
Thus why everyone hate and loves CVS ;-) 

I'll just note here that the workaround is to do a team/update immediately after
checkout. It's ugly, but it's what you'd have to do on the command line if you
wanted that to happen.

mike
Comment 2 Ed Burnette CLA 2004-05-21 18:00:48 EDT
Is this the same as bug 43112?
Comment 3 Michael Valenta CLA 2004-05-22 21:28:41 EDT
Looks the same to me (thanks Ed).

*** This bug has been marked as a duplicate of 43112 ***