Re: [platform-vcm-dev] Adding/Refreshing CVS resources programmatically

[birdo@xxxxxxxxxxxx (Roberto Scaramuzzi)]

On Wednesday 04 September 2002 05:49, you wrote:
> Roberto,
>
> Do you require that the resources be added to version control immediately
> or are you just concerned that a user may miss committing a resource? We've
> had the same problem with the .project file. We considered automatically
> adding it to version control but decided against it because some user do
> not want to (or can't) store this file in the repository. Our solution for
> CVS is to make it appearent to the user when files are not under version
> control (using decorators and prompting) but to make it easy for them to
> commit these files. To this end, commiting in the sync view will prompt to
> add unadded resources and the plan is to give this same behavior to Team >
> Commit (see bug 22372 http://dev.eclipse.org/bugs/show_bug.cgi?id=22372).
> Do you think that such facilities would be enough for you or do you really
> feel that you need a standard API to add resources?
>
> Michael

We've tried using the current setup, but it will involve putting unreasonable 
requirements on the user (interpreting cryptic CVS error messages and 
figuring out how to resolve conflicts, for example), so yes, we will really 
need a standard API to handle common operations (at least add, checkout, 
commit, update, and a hook to automatically resolve conflicts).

-- 
Roberto Scaramuzzi
System Engineer
Parasoft, Inc.