[news.eclipse.tools] Re: Towards improved CVS module support

[Michael Valenta <Michael_Valenta@xxxxxxx>]

KC,

Good point, I had forgotten about this case. I think the following 
behavior would be appropriate:

1. If the folder is moved to a project that is not shared with a 
repository, the project could be configured such that CVS operations 
performed on the project would only effect the moved folder.

2. If the folder is moved to a project shared with the same repository, 
the folder could be added and the CVS folders maintained.

3. If the folder is moved to a project that is mapped to another CVS 
repository or another repository provider, the CVS directories must be 
purged

For case 1 and 2, the ser would be prompted to carry out the operation 
or purge the CVS information.

Michael

KC Jones wrote:

> As a newbie I'd like to make one modest request:
>
> Eclipse should not destroy data without the consent of the user.
>
> Specifically, Eclipse should not destroy CVS support files
> and directories without user confirmation.  Maybe this
> should be configurable, but the default really ought to be
> non-destructive.
>
> Again, I'm a newbie and there is a good chance I simply
> missed the indoctrination rituals that explain why Eclipse
> enforces the One True Way of using CVS.  But in my ignorance
> I've managed to waste many, many hours recovering from
> Eclipse's penchant for purging CVS data when directory trees
> are moved around using Eclipse's resource view.
>
> Chances are good that any explicit support for modules will
> not involve checking a module out and then moving it.  But I
> would hope that while making Eclipse more flexible vis a vis
> modules, it can also be made more flexible w.r.t. moving
> directory trees that are under CVS control.
>
> Cheers,
> KC Jones
>
> leapfrog.com java developer
> using Version: 2.0
> Build id: 200206271827
> on Win2K