Re: [platform-vcm-dev] VCM 2.0 - question ...

["Kevin McGuire/OTT/OTI" <Kevin_McGuire@xxxxxxx>]

There are other cases of this too (with other repository types).

As Tim indicates, the *ideal* solution is to pick the repo type when 
creating the project, and allow it some control over the project location 
(at least in determining the default).

We don't yet know the best way to make that happen in the current Eclipse 
architecture.  There is some discussion going on regarding Project Natures 
that this may dovetail into, but we're still sorting that out.







"Tim Ellison" <Tim_Ellison@xxxxxxxxxx>
Sent by: platform-vcm-dev-admin@xxxxxxxxxxx
11/23/2001 10:42 AM
Please respond to platform-vcm-dev

 
        To:     platform-vcm-dev@xxxxxxxxxxx
        cc: 
        Subject:        Re: [platform-vcm-dev] VCM 2.0 - question ...


I think being able to directly create a new/existing project with a team
provider would be useful.

Regards,
Tim

Michael Valenta wrote:

> We encountered the same issues for the CVS client. We are still
> trying to determine the best mechanisms for this but this is how
> we do it now.
>
> - We have a checkout mechanism that is independant of team. We
> checkout a project and then, once it's loaded, we register it
> with the team provider.
>
> - When we place a new project from the workspace into the
> repository (i.e. Connect project to Team), we send it to the
> repository (using cvs import) and then check it out over top of
> the project to get the cvs generated information, then we
> register it with the team provider. You could check it out to
> the new location and remove or rename the original project.
>
> As for configure, the CVS client does nothing so far since everything is
> done ahead of time.
>
> Hope this helps
> Michael Valenta




                    Boris Pruessmann
                    <boris+mailinglists.platform-vcm-dev@prues        To:
<platform-vcm-dev@xxxxxxxxxxx>
                    smann.org>                                        cc:
                    Sent by:
Subject:     [platform-vcm-dev] VCM 2.0 - question ...
                    platform-vcm-dev-admin@xxxxxxxxxxx


                    23/11/2001 08:40 AM
                    Please respond to platform-vcm-dev






Hello all,

I am currently trying to develop a perforce integration for eclipse.
Taking a look at the current version, I realized that I might have a
problem
because of the way perforce works. Here we go:

- Perforce has one rootpath/client for all its operations. So, if my root
  path is c:\perforce all the controlled files will be under that path and
  its subdirectories.

- If I want to have my sources under source control, I have to assure that
  my projects are created under that root path. I don't think this is
  currently possible - at least there was no way to specify the team
  provider during the creation of a project, which would be necessary.

- The mechanism of configuring an existing project afterwards will not 
work

  because of the rootpath problem. The same for deconfiguring. If the
  project is under the rootpath, it's under control.

I could of course always copy the files between the two locations, but I
still want to be able to use the tools currently available ...

Any suggestion would be greatly appreciated :)

Regards,
Boris



_______________________________________________
platform-vcm-dev mailing list
platform-vcm-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-vcm-dev




_______________________________________________
platform-vcm-dev mailing list
platform-vcm-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-vcm-dev



_______________________________________________
platform-vcm-dev mailing list
platform-vcm-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-vcm-dev