[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-vcm-dev] Adding/Refreshing CVS resources programmatically
|
(Just back from vacation and picking up the thread)
>>We've tried using the current setup, but it will involve putting
unreasonable
>>requirements on the user (interpreting cryptic CVS error messages
So I'm curious how you envision these errors being handled? Do you expect
that your code will somehow interpret the error (from some provider neutral
API) and never display the CVS message to the user? I'm not sure how one
can write such clever code in general. Note: *all* we get from CVS are
cryptic strings that are a lot of work just to pull obvious information out
of, let alone do sophisticated programmatic error handling.
>> and figuring out how to resolve conflicts, for example)
I don't see how having an API is going to allow you to avoid the conflict
problem. There's automerge in CVS, but some conflicts can't be automerged.
For control/meta files, manual merging is generally preferred.
I haven't looked at Geoff's WVCM yet, but I assume that a repository
neutral API is unlikely to give you auto-merge on commit, since for example
in CVS merging is done on update, not on commit. Rather, most implementors
of the API (cvs included) would likely just return an error on the conflict
case and expect (you) the caller to sort it out. Or its a pessimistic
provider and you'ld fail on the checkout for conflicts. Geoff?
It seems that you are hoping an API will shield you from the intricacies of
the repository. I don't know of a way to make that true - the caller (you,
or the user) must always deal with such complications as you listed.
Kevin
birdo@xxxxxxxxxxxx
(Roberto Scaramuzzi) To: platform-vcm-dev@xxxxxxxxxxx
Sent by: cc:
platform-vcm-dev-admin@ Subject: Re: [platform-vcm-dev] Adding/Refreshing CVS
eclipse.org resources programmatically
09/05/2002 05:04 PM
Please respond to
platform-vcm-dev
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.
_______________________________________________
platform-vcm-dev mailing list
platform-vcm-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-vcm-dev
