RE: [platform-vcm-dev] Adding/Refreshing CVS resources programmat ically

["Clemm, Geoff" <gclemm@xxxxxxxxxxxx>]

As Kevin indicates, the SimpleAccessOperations API from Eclipse-1.0 was
not capable of interoperating successfully with many team providers,
and therefore was not made part of the Eclipse API.

But I agree that having a standard (headless) Team API is of significant
value in several use cases.

There currently is a standardization effort underway within the JCP
to define the "WVCM" API that is designed to provide effective
interoperation with
a wide range of team repositories (both versioning and non-versioning).

I believe that the WVCM API is suitable for use as the Eclipse (headless)
Team API,
and in order to ensure that the WVCM API meets the needs of the Eclipse
community (and in the spirit of the open source nature of the Eclipse
community),
I've posted the current version of the WVCM API at
http://www.webdav.org/deltav/wvcm
so that the Eclipse community can participate in the design of this API.

I'll start a new thread for this in the platform-vcm-dev mailing list,
titled "The WVCM API". 

Cheers,
Geoff


-----Original Message-----
From: Vladimir Grishchenko [mailto:vladgri@xxxxxxxxxxx]

What about SimpleAccessOperations? The only fact that it is optional renders
it pretty much useless for both repository providers and plugin writers.
IMHO having CVS supporting it would make a big difference, even if it was
still "optional".

----- Original Message -----
From: "Kevin McGuire" <Kevin_McGuire@xxxxxxx>

> This is correct - there is no API to span all providers.  In general I
> think you would find that IDE's which do support some kind of provider
> independent API require the resource to already be under version control
> anyway.  (Note: to head off your question, these APIs are known to be
> deficient for any interesting repository technology and so weren't
> encorporated into eclipse 2.0).
>
> We do have some interest in opening up some API points for CVS, but it
> would mean a CVS specific solution of course.
>
> Note that in CVS we have a special decorator for files that are not under
> version control yet not ignored, so this might help your users more than
> tasks which are often ignored by users.

-----Original Message-----
From: birdo@xxxxxxxxxxxx (Roberto Scaramuzzi)
>
> We are writing an Eclipse 2.0 plugin. Our plugin generates configuration
> files that are stored in a separate directory under the project root.
These
>
> files are usually created when the user presses OK in a Preference or
> Properties page.
>
> We would like to be able to add the configuration directory and any new
> configuration files that are generated to CVS (or whatever VCM provider is
> in
> use for the project) when they are created.
>
> If this is not possible, we would like to make it so that Eclipse will
> inform
> the user (maybe by generating a task) when these files are created, so
that
>
> the user can add them manually.
>
> As far as I can tell, all the CVS functionality is in internal packages,
> and
> the Team plugin does not provide any methods for adding/updating etc.
files
>
> and directories programmatically, so the only solution I see is for our
> plugin to generate cvsmarkers when new files are created or changed. I am
> not
> happy with this solution because it will only work with CVS and not other
> VCM
> providers.
>
> Is this correct, or am I missing something?