[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-vcm-dev] converting VCM to Team
|
The absence of migration API for 2.0 is in keeping with our original
position that there was no API in 1.0 and that we weren't supporting
third-party provider writing.
The way a provider stores sync info *should* be specific to that provider.
For example, in CVS we don't use sync info (except for managing
deleting-uncommitted resources), and neither does Clearcase.
I think this is a good opportunity for the community to be self-supporting
with common useful technology.
Also, I am not familiar with the contents of the draft you mention, but
perhaps a story that says "Users commit their projects prior to upgrading,
then check them out again" may be sufficient. This is a WebSphere issue
not an Eclipse one, so I can't speak with authority.
Kevin McGuire
"Vladimir Grishchenko"
<vladgri@xxxxxxxxxxx> To: <platform-vcm-dev@xxxxxxxxxxx>
Sent by: cc:
platform-vcm-dev-admin@ Subject: [platform-vcm-dev] converting VCM to Team
eclipse.org
06/26/02 09:25 PM
Please respond to
platform-vcm-dev
I got my hands on a "Ready for WebSphere Studio Software Integration
Requirements" draft. One of the required items for team integration is the
availability of "orderly migration of projects and resources to 2.0"
mechanism if VCM 1.0 was supported. I didn't see anything in the new API
that helps to accomplish this task. Does this mean that repository
providers
have to figure out internal stuff like how VCM1.0 stored sync info and
project sharing information and try to reconstruct it as a part of
migration
process? I can see that not all pieces of information might be needed for
every provider, but stuff like repository location seems required.
Just want to get an idea...
Thanks,
Vladimir.
_______________________________________________
platform-vcm-dev mailing list
platform-vcm-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-vcm-dev
